mcpbeat

Dd SDK Ios:git Branch

datadog/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.

355 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
286
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/DataDog/dd-sdk-ios --skill dd-sdk-ios:git-branch

The instruction itself

4 sections, as written by the author

Branching in dd-sdk-ios

Convention

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 description

Examples from the repo:

  • maxep/RUM-14622/visionos-integration-test
  • bplasovska/RUM-14563/lowercase-header-keys
  • kelvin/RUM-13420/cache-ddtags

Branch Model

The 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.

No JIRA Ticket?

For chores or external contributions without a ticket, use a descriptive slug only:

git checkout -b <author>/<slug> develop

How to use it

Copy the folder

Take datadog/dd-sdk-ios:git-branch from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.