skills.rest
axiomantic
axiomanticOFFICIAL
Explore all skills by this author →
GitHub

requesting-code-review

Coordinate pre-PR code review workflows with phase-gated exit criteria and SHA-based artifact persistence.

8|5|Updated Dec 30, 2025
Search Tags:#workflow#triage#code-review#artifact#gate#coordinate#pre-pr
One-click install
npx skills add https://github.com/axiomantic/spellbook --skill requesting-code-review-axiomantic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/axiomantic/spellbook/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/axiomantic/spellbook --skill requesting-code-review-axiomantic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams orchestrate and standardize pre-PR code review processes, ensuring consistent planning, triage, and governance before merging.

Core Features & Use Cases

  • Phase-gated review workflow: Plan, triage, and execute reviews across defined phases with artifact persistence.
  • Evidence-based findings: Require specific file evidence and maintain SHA-persistence for traceability.
  • Governance and compliance: Enforce exit criteria, gating rules, and re-review requirements to reduce risk.

Quick Start

Initiate a full pre-PR review cycle for a feature branch to generate a plan, triage findings, and produce a gate-ready report.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pre-PR code review coordination for my team?▼

Automate pre-PR code review coordination by orchestrating planning, triage, and execution phases with enforced exit criteria and SHA-based artifact persistence to ensure governance before merge.

What is a phase-gated code review workflow?▼

A phase-gated code review workflow divides the pre-PR process into planning, triage, and execution stages, requiring specific artifact persistence and evidence-based findings before advancing to the next phase.

How do I ensure evidence-based findings during code triage?▼

Ensure evidence-based findings during code triage by requiring specific file evidence and maintaining SHA-persistence for traceability throughout the pre-PR review cycle.

Can I enforce governance and compliance rules before merging code?▼

Enforce governance and compliance before merging code by applying gating rules, exit criteria, and re-review requirements that reduce risk and standardize the pre-PR workflow.

What's the best way to standardize code review triage across multiple feature branches?▼

Standardize code review triage across feature branches by initiating a full pre-PR review cycle that generates a plan, triages findings, and produces a gate-ready report.

Why do I need SHA-based artifact persistence for code reviews?▼

SHA-based artifact persistence provides traceability for evidence-based findings, ensuring that review artifacts remain linked to specific code states throughout the phase-gated workflow.

Related Skills

Explore More Software Engineering Skills→
onelee85onelee85

gsd-pr-branch

Filter .planning/ commits from a branch to produce a clean PR diff.

Community
Intermediate
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
coco-researchcoco-research
264

gsd-validate-phase

Audit completed phase validation coverage and reconstruct missing Nyquist validation evidence.

Community
Advanced
seanyofthedeadseanyofthedead

systematic-code-review

Automate a 4-phase code review process for pull requests.

Community
Advanced