| name | jira-pr-review |
| description | Move a Jira ticket from "In Development" to "In Review" using pull request context, populate Resolution Details when required, verify the transition, and produce an MS Teams review message. Use when asked to "move ticket to review", "send to in review", "update Jira with PR", or "ready for code review". Do not use for starting work, QA/PM signoff flows, merge readiness, or multi-stage board automation. |
Jira PR Review Workflow
Requires: GitHub CLI (gh) authenticated and Atlassian MCP configured.
Scope
- Handle only the board transition
In Development -> In Review.
- Do not automate QA/PM/Ready-to-Merge transitions in this skill.
- Only populate
Resolution Details when required by transition validation/screen rules or when the user explicitly asks for it.
Workflow
1) Resolve branch and PR context
git branch --show-current
gh pr list --head "<branch-name>" --json number,title,url,baseRefName,headRefName
gh pr view <pr-number> --json number,title,url,body,baseRefName,headRefName,commits
Rules:
- If no PR exists for the branch, stop and ask the user to create or open the PR first.
- Use PR commit subjects as the source for Resolution Details. Do not rely on
git log development..HEAD.
2) Resolve Jira key deterministically
Try in order:
- Branch name (
[A-Z]+-\d+)
- PR title
- PR body
If unresolved, ask the user for the ticket key.
3) Resolve Atlassian context by capability (intent first)
Capabilities to execute:
- Discover site/cloud context.
- Read Jira issue state and field name mapping.
