菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when public API changes have been made to review and update all *_FEATURE.md documentation files, or to audit whether they are still accurate.
Use when writing, reviewing, or renaming Swift APIs, including declarations, call sites, argument labels, Boolean names, protocols, overloads, documentation comments, and small abstractions.
Use when committing changes in dd-sdk-ios. Use when writing commit messages, signing commits, or staging files before a commit.
Use when creating a pull request in dd-sdk-ios. Use when writing PR titles, PR body, or choosing the target branch.
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.
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.
| name | dd-sdk-ios:git-branch |
| description | 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. |
Branch names follow: <author>/<JIRA-TICKET>/<descriptive-slug>
<author>: your GitHub username or initials<JIRA-TICKET>: project shortname + ticket number (e.g. RUM-9999, FFL-123)<descriptive-slug>: short kebab-case descriptionExamples from the repo:
maxep/RUM-14622/visionos-integration-testbplasovska/RUM-14563/lowercase-header-keyskelvin/RUM-13420/cache-ddtagsThe repo follows git-flow: master is production, develop is the integration branch.
For a single PR, branch from develop:
git checkout -b <author>/<JIRA-TICKET>/<slug> develop
For large contributions split across multiple PRs, create a shared feature branch first, then branch each PR from it:
git checkout -b feature/<feature-slug> develop # shared target branch
git checkout -b <author>/<JIRA-TICKET>/<slug> feature/<feature-slug> # per-PR branch
Each per-PR branch targets feature/<feature-slug>. Only the final feature branch is merged into develop.
For chores or external contributions without a ticket, use a descriptive slug only:
git checkout -b <author>/<slug> develop