← ClaudeAtlas

pr-review-with-ticket-contextlisted

Use when asked to review a GitHub pull request against its Jira ticket or bug report, especially a bug fix (for example "review PR 123 for ABC-456"), or to check whether a PR really fixes the root cause of the ticket's bug before approving it.
teransarathchandra/agent-skills · ★ 0 · Code & Development · score 78
Install: claude install-skill teransarathchandra/agent-skills
# PR review with ticket context Review a PR the way a teammate would: short, plain comments the author can act on, backed by code evidence. Produce two outputs: what to say **on the PR**, and what the PR **does not cover** but should. This skill pairs well with a root-cause-first debugging skill such as `superpowers:systematic-debugging`. If you do not have one, step 4 below stands on its own. ## Privacy rules (non-negotiable) Ticket text often holds names, emails, record keys, dates and quotes from real users. - Never copy user names, emails, record keys or quotes into: the final answer, subagent prompts, files, PR comments, ticket comments, memory, or any external service. - Describe the problem generically ("a user", "the second item is missing after save"). - Read the ticket through the MCP yourself. Give subagents only a generic bug description plus the code location. - Read-only: never comment on the PR or ticket, push, or edit files unless the user asks. - When the user asks you to post, show the exact comments first and post after their go-ahead, unless they said to post without review. Post only Section A rows of Medium and above, each anchored to its changed line. Section B goes to the ticket as notes or follow-ups, never to the PR. ## Steps 1. **Get the PR.** Run `gh pr view <n> --json title,body,baseRefName,headRefName,headRefOid,files`. Check out the branch in the right repo (the user may keep several repos side by side). - If `git pull` refuses because