mk:jira-dev
What This Skill Does
Forks the jira-dev agent to generate developer-side artifacts from a Jira ticket — branch names, PR descriptions, commit parsing, smart-commit linking. Pure artifact generation; the user reviews and runs the resulting git/gh commands.
When to Use
- Triggers: "branch name for PROJ-123", "PR description for PROJ-123", "parse commits for issue keys", "link this PR to PROJ-123"
- NOT for: executing git operations directly (use
mk:ship) · issue CRUD (mk:jira-issue).
Verified Wrapper Invocations
| Operation | Tier | Invocation |
|---|---|---|
| Branch name | 1 | ... dev branch-name PROJ-123 |
| PR description | 1 | ... dev pr-description PROJ-123 |
| Parse commits for keys | 1 | ... dev parse-commits --range main..HEAD |
| Link commit | 2 | ... dev link-commit PROJ-123 --sha <SHA> |
| Link PR | 2 | ... dev link-pr PROJ-123 --pr-url https://github.com/.../pull/N |
| Get issue commits | 1 | ... dev get-commits PROJ-123 |
Branch-Name Convention
Default jira-as output: <type>/<KEY>-<kebab-summary> (e.g. feat/PROJ-123-add-login-rate-limiting). Slug capped ~50 chars.
PR-Description Convention
pr-description synthesizes:
- Ticket summary → PR title
- Ticket description excerpt → PR body
- Acceptance criteria → checklist
- "Closes PROJ-123" footer (Atlassian smart-commit format)
Pipe into gh pr create for one-shot flow.
Domain References
references/branch-naming.md— convention referencereferences/smart-commits.md— smart-commit syntax (close / transition from commit messages)references/commit-messages.md— Atlassian-aware commit-message conventions
Peer Leaves
mk:ship (consumes dev branch-name + dev pr-description — handoff documented, no auto-wire) · mk:jira-issue (issue must exist before branch creation) · mk:jira-lifecycle (transitions via smart-commit footer)
Agent
jira-dev — A + C, NOT B.