requesting-code-review
/requesting-code-review
Use when implementation is done and you need a structured pre-PR review workflow. Triggers: 'ready for review', 'review my changes before PR', 'pre-merge check', 'is this ready', 'submit for review'. NOT for: post-merge review (use code-review) or deciding how to integrate (use finishing-a-development-branch).
- Author
- axiomantic ↗
- Repository
- spellbook ↗
- Licence
- MIT
- Last repository change
- 17.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 17.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when implementation is done and you need a structured pre-PR review workflow. Triggers: 'ready for review', 'review my changes before PR', 'pre-merge check', 'is this ready', 'submit for review'. NOT for: post-merge review (use code-review) or deciding how to integrate (use finishing-a-development-branch).
Triggers from the description
Original author description
Use when implementation is done and you need a structured pre-PR review workflow. Triggers: 'ready for review', 'review my changes before PR', 'pre-merge check', 'is this ready', 'submit for review'. NOT for: post-merge review (use code-review) or deciding how to integrate (use finishing-a-development-branch).
How it works
- Invariant Principles
- Phase-Gated Workflow
- Gate Rules
SKILL.md preview
--- name: requesting-code-review description: "Use when implementation is done and you need a structured pre-PR review workflow. Triggers: 'ready for review', 'review my changes before PR', 'pre-merge check', 'is this ready', 'submit for review'. NOT for: post-merge review (use code-review) or deciding how to integrate (use finishing-a-development-branch)." intro: | Pre-PR structured review that assembles context, dispatches review agents, triages findings by severity, and produces a remediation plan. Ensures every critical finding is addressed before merge by orchestrating the full review lifecycle from planning through quality gate. A core spellbook capability for when implementation is complete and you want a thorough check before creating a PR. --- # Requesting Code Review <ROLE> Self-review orchestrator. Coordinates pre-PR code review workflow. Your reputation depends on every Critical finding being fixed before merge — a missed Critical is a production defect you signed off on. </ROLE> <analysis> Before starting review workflow, analyze: 1. What is the scope of changes? (files, lines, complexity) 2. Is there a plan/spec document to review against? 3. What is the current git state? (branch, merge base) 4. What phase should we resume from if this is a re-review? </analysis> ## Invariant Principles 1. **Phase gates are blocking** - Never proceed to next phase without meeting exit criteria 2. **Evidence over opinion** - Every finding must cite specific code location and behavior 3. **Critical findings are non-negotiable** - No Critical finding may be deferred or ignored 4. **SHA persistence** - Always use reviewed_sha from manifest, never current HEAD 5. **Traceable artifacts** - Each phase produces artifacts for resume and audit capability <FORBIDDEN> - Proceeding past Phase 6 gate with unfixed Critical findings - Making findings without specific file:line evidence - Using current HEAD instead of reviewed_sha for inline comments - Skipping re-review when fix adds >100 lines or modifies new files - Deferring Critical findings for any reason </FORBIDDEN> <reflection> After each phase, verify: - Did we meet all exit criteria before proceeding? - Are all findings backed by specific evidence? - Did we persist the correct SHA for future reference? - Is the artifact properly saved for traceability? </reflection> ## Phase-Gated Workflow Reference: `patterns/code-review-formats.md` for output schemas. ### Phases 1-2: Planning + Context Determine git range, list changed files, identify plan/spec, estimate complexity. Assemble reviewer context bundle: plan excerpts, related code, prior findings. **Execute:** `/request-review-plan` **Outputs:** Review scope definition, reviewer context bundle **Self-Check:** Git range defined, file list confirmed, context bundle ready for dispatch. ### Phases 3-6: Dispatch + Triage + Execute + Gate Invoke code-reviewer agent, triage findings by severity, fix in Critical-first order, apply quality gate for proceed/block decision. **Execute:** `/request-review-execute` **Outputs:** Review findings, triage report, fix report, gate decision **Self-Check:** Valid findings received, triaged, blocking findings addressed, clear verdict. ### Artifact Contract Directory structure, phase artifact table, manifest schema, and SHA persistence rule. **Reference:** `/request-review-artifacts` ## Gate Rules Reference: `patterns/code-review-taxonomy.md` for severity definitions. ### Blocking Rules | Condition | Result | |-----------|--------| | Any Critical unfixed | BLOCKED - must fix before proceed | | Any High unfixed without rationale | BLOCKED - fix or document deferral | | >=3 High unfixed | BLOCKED - systemic issues | | Only Medium/Low/Nit unfixed | MAY PROCEED | Deferral rationale must be written justification citing the specific constraint (risk acceptance, blocked dependency, or explicit product decision) — "will fix later" does not qualify. <CRITICAL> Always use `reviewed_sha` from manifest for inline comments. Never query current HEAD - commits may have been pushed since review started. </CRITICAL> <FINAL_EMPHASIS> Every gate in this workflow exists because defects discovered post-merge cost 10x more to fix. Do not skip phases. Do not defer Criticals. Do not let SHA drift corrupt inline comments. A review that lets one Critical through is worse than no review at all. </FINAL_EMPHASIS>
Files in this package (2)
- SKILL.md 4 KB
- code-reviewer.md 3 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · axiomantic/spellbook | 90 | MIT |
| GanyuanRan/Aegis | 100 | MIT |
| event4u-app/agent-config | 100 | MIT |
| osmontero/opencode-skills | 100 | MIT |
| jjuraszek/pi-gauntlet | 100 | MIT |
| seaworld008/commonly-used-high-value-skills | 100 | MIT |
| FrancoStino/opencode-skills-collection | 100 | MIT |
| nikospavlopoulos/devops-mutant-powers | 100 | MIT |
| coco-research/coco | 100 | MIT |
Database snapshot: 13.11.2026 · package version b88aebb9b5b8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup - 100finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup - 100finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup - 100review
Use when code changes need review for security, cost, architecture, or acceptance criteria verification. Triggers on /review, after implementation, pre-merge. - 96code-review
Use when reviewing GitHub CLI (gh) pull requests. - 100finishing-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work