메뉴
Perform thorough code review on a PR using the Pragmatic Quality framework. Integrates with Jira to validate implementation matches ticket requirements. Use when reviewing pull requests or providing PR feedback.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Identify and remove AI slop from code comments, documentation, and prose. Use when cleaning up AI-generated output, reviewing for AI tells, or improving signal-to-noise ratio in any text.
Design review for front-end code changes using Playwright for live browser testing. Covers visual hierarchy, accessibility (WCAG AA+), responsive design, and interaction patterns. Use when reviewing UI/UX changes before merge.
Adversarial code review that assumes the worst. Finds failure modes, race conditions, blast radius, and edge cases that optimistic reviewers miss. Use when you want brutal honesty about code resilience.
Validate implementation plans for completeness, specificity, and actionability. Catches vague language, missing sections, and untestable outcomes.
Interactive PRD creation and iteration for non-technical users. Use this skill whenever the user wants to define product requirements, write a PRD, spec out a feature, describe what to build, or says "what should we build", "write requirements", "create a PRD", "define the product". Also use when updating an existing PRD based on stakeholder or engineering feedback. Guides through structured requirement definition using plain-language facilitation prompts with discovery questions upfront. Auto-validates with /prd-validator after completion.
Translates an approved PRD into a unified ROADMAP.md with phased feature descriptions and implementation checklists. Use this skill whenever an engineer receives a PRD and needs to break it into phases, when the user asks "how do I turn this PRD into a plan", "create a roadmap from requirements", or "decompose this into milestones". Gates on PRD validation — refuses to proceed if the PRD hasn't passed /prd-validator.
| name | code-review |
| description | Perform thorough code review on a PR using the Pragmatic Quality framework. Integrates with Jira to validate implementation matches ticket requirements. Use when reviewing pull requests or providing PR feedback. |
| context | fork |
| agent | pragmatic-code-review |
| model | opus |
| allowed-tools | Bash(git diff:*), Bash(git log:*), Bash(git show:*), Bash(git status), Bash(git branch:*), Bash(gh pr view:*), Bash(gh pr diff:*), Grep, Glob, LS, Read, WebFetch, TodoWrite |
| tags | ["review"] |
| tier | core |
Review the pending changes using the Pragmatic Quality framework.
GIT STATUS:
!`git status`
PR METADATA:
!`gh pr view --json title,body,author,files,additions,deletions,headRefName,state 2>/dev/null || echo "No PR context - reviewing local branch"`
FILES MODIFIED:
!`gh pr diff --name-only 2>/dev/null || git diff --name-only origin/HEAD...`
COMMITS:
!`gh pr view --json commits --jq '.commits[].messageHeadline' 2>/dev/null || git log --oneline origin/HEAD...`
DIFF CONTENT:
!`gh pr diff 2>/dev/null || git diff --merge-base origin/HEAD`
If Atlassian MCP is connected, fetch linked ticket details and validate implementation against acceptance criteria.
Use the pragmatic-code-review agent to review the complete diff above. Your final reply must contain the markdown report.
scripts/pr-context.sh 123 # Fetch PR metadata via gh
scripts/extract-ticket-ids.sh 123 # Extract Jira IDs from PR
python scripts/diff-analysis.py --staged # Analyze diff patterns
references/REVIEW_CHECKLIST.md — Detailed checklistassets/feedback-templates.md — Common feedback patterns