Menu
Use when creating a pull request in dd-sdk-ios. Use when writing PR titles, PR body, or choosing the target branch.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 new branch in dd-sdk-ios for a JIRA ticket or feature. Use when choosing a branch name or base branch for development work.
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:open-pr |
| description | Use when creating a pull request in dd-sdk-ios. Use when writing PR titles, PR body, or choosing the target branch. |
[PROJECT-XXXX] 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[PROJECT-XXXX] matching the JIRA ticketdevelopThe repo has a PR template at .github/PULL_REQUEST_TEMPLATE.md. Read it and fill in all sections.
Before pushing, show the user the commits that will be pushed and ask for confirmation:
git log origin/develop..HEAD --oneline
Ask: "Shall I push these commits and open the PR?" Only proceed after the user confirms.
Before running the command, show the user the proposed PR title and full body and ask for confirmation. Only run gh pr create after the user approves.
gh pr create \
--title "[RUM-9999] Your title here" \
--body "<filled-in PR body following .github/PULL_REQUEST_TEMPLATE.md>" \
--base develop \
--draft
Never add Co-Authored-By: Claude or any AI co-author trailer to the PR body or commits.
make lint passesmake test-ios-all passesmake api-surface-verify passes (if public API changed)| Mistake | Fix |
|---|---|
| Wrong base branch | Always develop, not main or master |
Missing [PROJECT-XXXX] title prefix | Required for internal work |
| Skipping review checklist items | Fill out checklist before marking PR ready |