review
starsforks
How to install review?
owainlewis/blueprint/review
$npx -y skills add owainlewis/blueprint --skill reviewIndependently reviews code for correctness, security, regressions, unnecessary complexity, and missing tests or evidence. Use when the user asks for a code review, PR review, diff review, security review, second opinion, or pre-merge review. Launches a fresh subagent and never ed
SKILL.md
| 1 | # Review |
| 2 | |
| 3 | The reviewer must be a fresh subagent that did not implement the change. Do not edit files. |
| 4 | |
| 5 | ## Workflow |
| 6 | |
| 7 | 1. Give the reviewer the task, acceptance criteria, repository guidance, diff or PR, and test evidence. |
| 8 | 2. Have it read the relevant surrounding code and try to prove the change wrong. Check behavior, edge cases, failures, security boundaries, interfaces, compatibility, regressions, scope, complexity, and whether tests exercise the changed behavior. |
| 9 | 3. Have it run focused checks when practical. |
| 10 | 4. Return actionable findings in severity order. For each finding give the location, impact, evidence, and smallest fix direction. |
| 11 | |
| 12 | - **blocker:** unsafe to merge. |
| 13 | - **important:** should fix before merge. |
| 14 | - **nit:** optional; omit unless asked. |
| 15 | |
| 16 | ## Verdict |
| 17 | |
| 18 | If fresh subagents are unavailable, stop and report that independent review is blocked unless the user explicitly accepts a documented self-review. |
| 19 | |
| 20 | If there are no findings, say so. End with `Approve`, `Request changes`, or `Blocked`, then state what remains unverified. |
| 21 | |
| 22 | ## Boundaries |
| 23 | |
| 24 | - Review only the change. |
| 25 | - Do not turn preferences into findings. |
| 26 | - Do not approve solely because checks pass. |
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
