pr-review-agent
starsforks
How to install pr-review-agent?
wednesday-solutions/ai-agent-skills/pr-review-agent
$npx -y skills add wednesday-solutions/ai-agent-skills --skill pr-review-agentFull PR review orchestrator. Use when asked to review a PR or check if it is ready to merge. Runs blast radius + drift check on changed files, then hands off to pr-review for comment triage and fixes. Do NOT use pr-review directly for full reviews — use this.
SKILL.md
| 1 | # PR Review Agent |
| 2 | |
| 3 | ## When to use |
| 4 | - "Review this PR" |
| 5 | - "Is this PR ready to merge?" |
| 6 | - "Check this PR for issues" |
| 7 | - PR is open and review comments have been posted |
| 8 | |
| 9 | ## What to do |
| 10 | |
| 11 | 1. **triage-read** — Fetch all review comments via `gh pr view --comments`. Sort by impact: security → breaking → logic → performance → naming → style. Present the full categorised list to the dev. |
| 12 | |
| 13 | 2. **In parallel:** |
| 14 | - **brownfield-fix** — Run `wednesday-skills score` and `wednesday-skills blast` on every file changed in the PR. Flag any file with risk > 60. |
| 15 | - **brownfield-drift** — Run `wednesday-skills drift --since <base-sha>`. Report any architecture violations introduced by this PR. |
| 16 | |
| 17 | 3. Present a unified report: |
| 18 | - Review comments (categorised) |
| 19 | - High-risk changed files (score + dependent count) |
| 20 | - Architecture violations (if any) |
| 21 | |
| 22 | 4. **triage-fix** — Wait for dev approval: "@agent fix #N" or "@agent fix all". Apply fixes in priority order. Read git-os skill before committing. One commit per fix item. |
| 23 | |
| 24 | ## Never |
| 25 | - Fix without explicit dev approval |
| 26 | - Skip blast radius check — always run even for small PRs |
| 27 | - Skip drift check — always run even if no violations are expected |
| 28 | - Bundle multiple file fixes in one commit |
| 29 | - Force-push or silently skip a failed fix |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
