dd-sdk-ios:git-commit
Use when committing changes in dd-sdk-ios. Use when writing commit messages, signing commits, or staging files before a commit.
Best use case
dd-sdk-ios:git-commit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when committing changes in dd-sdk-ios. Use when writing commit messages, signing commits, or staging files before a commit.
Teams using dd-sdk-ios:git-commit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/git-commit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How dd-sdk-ios:git-commit Compares
| Feature / Agent | dd-sdk-ios:git-commit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when committing changes in dd-sdk-ios. Use when writing commit messages, signing commits, or staging files before a commit.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Committing in dd-sdk-ios ## Requirements - **All commits MUST be signed** (GPG or SSH) - **Message prefix**: `[PROJECT-XXXX]` matching the JIRA ticket (internal development only) ## Message Format ``` [RUM-9999] Short imperative description ``` **Examples:** - `[RUM-1234] Add baggage header merging support` - `[FFL-213] Add Feature Flags support` - `[RUM-14655] Fix WebView log events attaching incomplete ddTags` Third-party contributions skip the prefix. ## Commit Command ```bash git commit -S -m "[RUM-9999] Your message here" ``` The `-S` flag applies your configured GPG/SSH signature. **Never add `Co-Authored-By: Claude` or any AI co-author trailer to commits in this repo.** ## Common Mistakes | Mistake | Fix | |---------|-----| | Missing signature | Always use `-S`; check `git log --show-signature -1` | | Missing `[PROJECT-XXXX]` prefix | Required for internal dev; skipped for third-party | | New files missing from pbxproj | Use Xcode MCP tools — see `xcode-file-management` skill | | Adding `Co-Authored-By: Claude` trailer | Never add AI co-author trailers in this repo |
Related Skills
dd-sdk-ios:xcode-file-management
Use when adding, removing, moving, or renaming Swift source files in the dd-sdk-ios Xcode project. Use when the task involves file creation, deletion, or relocation in any module (DatadogRUM, DatadogLogs, DatadogCore, etc.). Use when you would otherwise reach for Write, Bash mv/mkdir/rm, or manual pbxproj editing for file management.
dd-sdk-ios:running-tests
Use when asked to run tests in the dd-sdk-ios project — whether a full module suite, a specific test class, or a single test method. Use when choosing between make, xcodebuild, or Xcode MCP for running iOS/tvOS/visionOS tests.
dd-sdk-ios:open-pr
Use when creating a pull request in dd-sdk-ios. Use when writing PR titles, PR body, or choosing the target branch.
dd-sdk-ios:git-branch
Use when creating a new branch in dd-sdk-ios for a JIRA ticket or feature. Use when choosing a branch name or base branch for development work.
commit
ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.
git-commit-helper
Generate standardized git commit messages following Conventional Commits format. Use this skill when the user asks to commit code, write a commit message, or create a git commit. Enforces team conventions for type prefixes, scope naming, message length, and breaking change documentation.
git-commit
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
conventional-commit
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.
commit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
commit-work
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
commit-smart
Analyze staged/unstaged changes and create semantic conventional commits with context about WHY, not just WHAT. Auto-detects commit type and scope from the diff. Supports optional type/scope arguments. Usage - /commit-smart, /commit-smart fix, /commit-smart refactor api
Git Commit Helper
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.