gated-review
Provides parallel, multi-stage code reviews to find blind spots after implementation.
Install
mkdir -p .claude/skills/gated-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11499" && unzip -o skill.zip -d .claude/skills/gated-review && rm skill.zipInstalls to .claude/skills/gated-review
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Find blind spots that implementers miss through independent, layered verification. Use when the user has finished implementing a feature or fix and wants thorough verification before integrating. Make sure to use this skill whenever implementation is done, even if the user says 'it works, just push it.' DO NOT TRIGGER for: typo-only fixes, README/documentation-only changes, config file changes, formatting/linting commits, or dependency version bumps with no code changes.Key capabilities
- →Dispatch `ironflow:spec-compliance-reviewer` subagent for spec compliance review
- →Dispatch `ironflow:code-quality-reviewer` subagent for code quality review
- →Dispatch `ironflow:reuse-reviewer` subagent for reuse and pattern review (large projects only)
- →Collect and merge findings from multiple reviewer subagents
- →Coordinate fixes with the implementer based on review findings
- →Gate progression between review phases
How it works
The orchestrator agent dispatches reviewer subagents in parallel for spec compliance, code quality, and reuse review. It collects their findings, coordinates fixes, and gates progression to serial verification stages like full regression and smoke tests.
Inputs & outputs
When to use gated-review
- →Reviewing feature implementation
- →Bug fix verification
- →Spec compliance check
- →Integration gatekeeping
About gated-review
Coordinates subagents to independently verify spec compliance, code quality, and testing regressions. Acts as a gatekeeper to ensure code meets standards before integration.
Find blind spots that implementers miss through independent, layered verification. Use when the user has finished implementing a feature or fix and wants thorough verification before integrating. Make sure to use this skill whenever implementation is done, even if the user says 'it works, just push
When not to use it
- →When the changes are typo-only fixes
- →When the changes are documentation-only (README)
- →When the changes are config file changes, formatting/linting commits, or dependency version bumps with no code changes
Limitations
- →The skill does not trigger for typo-only fixes, documentation-only changes, config file changes, formatting/linting commits, or dependency version bumps with no code changes.
- →Reuse and Pattern Review is only for large projects (monorepo, modular-packages, enterprise codebase).
- →The process involves two main phases: Parallel Code Review and Serial Verification.
How it compares
This skill uses independent, layered verification by multiple subagents to find blind spots, unlike a single manual review.
Compared to similar skills
gated-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gated-review (this skill) | 0 | 4mo | Review | Advanced |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| test-cases | 57 | 7mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
test-cases
cexll
This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.
reviewing-code
CaptainCrouton89
Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.
wcag-audit-patterns
wshobson
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.
code-coverage-with-gcov
gadievron
Add gcov code coverage instrumentation to C/C++ projects