Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/git-branch
SKILL.md
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-testbplasovska/RUM-14563/lowercase-header-keyskelvin/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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?