メニュー
Full Jira-tracked change workflow — create/select Jira ticket under epic SDK-5256, create feat/SDK-XXXX branch, commit with ticket id, push, and open PR with ticket id in title and Jira links in body
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create git commit following project conventions
Generate test JSON configurations following JSON_STRUCTURE_REFERENCE.md rules
Review code changes against project standards and conventions
Show current project status and development phase progress
Run tests for Android or iOS SDK
| name | ship-jira |
| description | Full Jira-tracked change workflow — create/select Jira ticket under epic SDK-5256, create feat/SDK-XXXX branch, commit with ticket id, push, and open PR with ticket id in title and Jira links in body |
| user-invocable | true |
| disable-model-invocation | false |
End-to-end workflow for any tracked change to this repo. Every change ships through Jira: ticket → branch → commit → push → PR. The ticket id is in the branch name, commit subject, and PR title.
/ship-jira [SDK-XXXX] # use existing ticket
/ship-jira "<short summary>" # create new ticket under epic SDK-5256
/ship-jira # ask: existing or new?
SDK-XXXX): fetch it via mcp__claude_ai_Atlassian__getJiraIssue to confirm it exists and is under the right epic.mcp__claude_ai_Atlassian__createJiraIssue. Required fields:
cloudId: wizrocket.atlassian.netprojectKey: SDKissueTypeName: Taskparent: SDK-5256additional_fields: {"customfield_10441": [{"value": "Release Notes"}]} ← Documentation Required, mandatory custom field; valid values are "Release Notes" or "Dev Docs". Choose Dev Docs for internal API/dev-doc work, Release Notes for user-visible changes.description: structured (Goal / Scope / Validation / Out of scope)feat/SDK-XXXX-<kebab-slug> (preferred) or task/SDK-XXXX-<slug> / fix/SDK-XXXX-<slug> for non-feature work.release/native-display-v1 — verify with git branch --show-current on a fresh checkout, or check the most recent merged PR's base).git checkout -b feat/SDK-XXXX-tighten-sdk-visibility
git add -AUse the working tree to identify files actually touched by this change. Skip files that pre-date the session (check initial git status for the conversation). git add <file1> <file2> … — explicit list, no wildcards. Common false-positives: version-bump edits in sample build.gradle.kts, runtime artifacts, .claude/scheduled_tasks.lock.
Commit subject must lead with the ticket id:
SDK-XXXX: <imperative description> (Android | iOS | Android + iOS)
Body explains why (constraint, deadline, prior incident) and lists the what per platform. End with:
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Pass via heredoc to preserve formatting:
git commit -m "$(cat <<'EOF'
SDK-XXXX: <subject>
<body>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
EOF
)"
git push -u origin feat/SDK-XXXX-<slug>
Use mcp__github__create_pull_request:
CleverTapclevertap-native-ui-kitrelease/native-display-v1 (verify against most recent merged PR's base.ref)feat(SDK-XXXX): <description> — ticket id in parentheses, conventional-commit prefix## Jira — link to SDK-XXXX and parent epic SDK-5256## Summary — what changed and why now## Changes — per-platform tables (### Android / ### iOS)## Compatibility — source-compat impact## Test plan — checkboxes; what passed locally vs. what reviewer must verify## Out of scope (optional)[SDK-XXXX]: https://wizrocket.atlassian.net/browse/SDK-XXXX and [SDK-5256]: …🤖 Generated with [Claude Code](https://claude.com/claude-code)# Existing ticket
/ship-jira SDK-5780
# New ticket — skill creates it under SDK-5256 first
/ship-jira "Tighten SDK visibility/access modifiers for v1 release"
# Hotfix — use fix/ prefix
/ship-jira SDK-5781 # branch becomes fix/SDK-5781-… if commit type is fix
feat/, task/, fix/. Match the commit-type prefix to the branch prefix.feat(SDK-XXXX): — recent style — or SDK-XXXX: (older). Prefer feat(SDK-XXXX): for new work.release/native-display-v1. Re-verify if the release branch rotates.SDK on wizrocket.atlassian.net.Every Task creation under project SDK requires customfield_10441 (Documentation Required) with a value of either Release Notes or Dev Docs. The skill MUST include this in additional_fields or the API call will fail with "Documentation Required is required.".
git add -A / git add . — always stage by explicit path.main, release/*, or any shared branch — only to the feat branch.--force-push.--no-verify.Done / Closed to repurpose it — create a new one./commit (which enforces the commit-message format) and adds the branch + push + PR steps./review (run before opening PR) and /build + /test (run before committing).