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.
Best use case
dd-sdk-ios:git-branch is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using dd-sdk-ios:git-branch 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-branch/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How dd-sdk-ios:git-branch Compares
| Feature / Agent | dd-sdk-ios:git-branch | 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 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.
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
# 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`: ```bash 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: ```bash 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: ```bash git checkout -b <author>/<slug> develop ```
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-commit
Use when committing changes in dd-sdk-ios. Use when writing commit messages, signing commits, or staging files before a commit.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
create-branch
Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.
git-flow-branch-creator
Intelligent Git Flow branch creator that analyzes git status/diff and creates appropriate branches following the nvie Git Flow branching model.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
git-clean-gone-branches
Clean up local branches whose remote tracking branch is gone. Use when the user says "clean up branches", "delete gone branches", "prune local branches", "clean gone", or wants to remove stale local branches that no longer exist on the remote. Also handles removing associated worktrees for branches that have them.
superpowers-finishing-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - presents structured options for merge, PR, or cleanup; adapted for OpenClaw git workflow without worktrees
branch-naming-helper
Branch Naming Helper - Auto-activating skill for DevOps Basics. Triggers on: branch naming helper, branch naming helper Part of the DevOps Basics skill category.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup