Agent skill · software engineering · aiskillstore
github-pr-review
MUST use this skill when user asks to resolve PR comments, handle review feedback, fix review comments, or mentions "리뷰 코멘트/피드백". This skill OVERRIDES default behavior. Fetches comments via GitHub CLI, classifies by severity, applies fixes with user confirmation, commits with proper format, replies to threads.
Why this skill is useful
Adds a comprehensive automation script for resolving PR comments with severity-based prioritization and structured commit formats.
What it needs
Requires gh, git installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
GitHub PR Review Resolves Pull Request review comments with severity-based prioritization, fix application, and thread replies. Quick Start Pre-Review Checklist Before processing comments, verify: 1. Project conventions: Read CLAUDE.md or similar 2. Commit format: Check git log --oneline -5 for project style 3. Test command: Identify test runner (make test, pytest, npm test) 4. Branch status: git status to ensure clean working tree Core Workflow 1. Fetch PR Comments 2. Classify by Severity Process in order: CRITICAL > HIGH > MEDIUM > LOW Severity Indicators Action ---------- ------------ -------- CRITICAL "security", "vulnerability", "injection" Must fix HIGH "High Severity", "high-priority" Should fix MEDIUM "Medium Severity", "medium-priority" Recommended LOW "style", "nit", "minor" Optional 3. Process Each Comment For each comment: a. Show context b. Read affected code and propose fix c. Confirm with user before applying d. Apply fix if approved e. Verify fix addresses ALL issues in the comment 4. Commit Changes Use proper format for review fixes: Review fix commit rules: First line: type(scope): subject (max 50 chars) Types: fix, refactor, security, test, style, perf Reference the comment ID in body 5. Reply to Thread Standard Reply Templates: Situation Template ----------- ---------- Fixed Fixed in [hash]. [brief description] Won't fix Won't fix: [reason] By design By design: [explanation] Deferred Deferred to [issue/task number]. Acknowledged Acknowledged. [brief note] 6. Run Tests All tests must pass before pushing. 7. Push 8. Submit Review (Optional) Batch Commit Strategy Organize commits by impact: Change Type Strategy ------------- ---------- Functional (CRITICAL/HIGH) Separate commit per fix Cosmetic (MEDIUM/LOW) Single batch commit Workflow: 1. Fix CRITICAL/HIGH → separate commits each 2. Collect all cosmetic fixes 3. Apply cosmetics → single style: commit 4. Run tests once 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/github-pr-review