speckit-review-run
Skill548 starsChanged 12 days agoApache-2.0View on GitHub
Comprehensive code review using specialized agents — orchestrates code,
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- haru/redmine_ai_helperedited, first seen Feb 14, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- haru/redmine_ai_helper★ 10797% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository54 other files it gives its agents.
- AGENTS.mdAGENTS.md
- backend/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- backend/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- analyzing-ci-flakinessSkill
- audit-docsSkill
- commitSkill
- creating-changelog-entriesSkill
- creating-issuesSkill
- creating-prdSkill
- grilling-ideasSkill
- harvesting-reviewSkill
- migrate-feature-pageSkill
- monitoring-pull-requestsSkill
- neo4j-cypher-guideSkill
- opsmill-dev-analyzing-bugsSkill
- opsmill-dev-fixing-bugsSkill
- opsmill-dev-test-driving-bugsSkill
- pre-ciSkill
- prSkill
- rebaseSkill
- reviewing-pull-requestsSkill
- speckit-agent-context-updateSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-critique-runSkill
- speckit-git-commitSkill
- speckit-git-featureSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-opsmill-autoSkill
- speckit-opsmill-extractSkill
- speckit-opsmill-implementSkill
- speckit-opsmill-prepSkill
- speckit-opsmill-retrospectSkill
- speckit-opsmill-summarySkill
- speckit-planSkill
- speckit-review-codeSkill
- speckit-review-commentsSkill
- speckit-review-errorsSkill
- speckit-review-simplifySkill
- speckit-review-testsSkill
- speckit-review-typesSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- upgrading-infrastructure-dependenciesSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Run a comprehensive pull request review using multiple specialized agents, each focusing on a different aspect of code quality.
- Very specific: line 20
Read the project config file at .specify/extensions/review/review-config.yml (if it exists).
- Very specific: line 21
If the file does not exist, fall back to the defaults.agents section in the extension's extension.yml.
- Distinctive: line 27
If specific aspects were requested, run exactly those — config toggles do not apply (explicit user request overrides config).
- Distinctive: line 28
Default (no arguments): Run all applicable reviews that are enabled in config.
- Distinctive: line 34
errors: - Check error handling for silent failures
- Distinctive: line 38
all: - Run all applicable reviews (default)
- Distinctive: line 42
If the user provided a file list or explicit instructions on how to retrieve files (e.g., only staged, only unstaged, a specific folder, …
- Distinctive: line 59
If an agent is disabled by config, note it in the final summary (e.g., "simplify: skipped (disabled in config)").
- Distinctive: line 75
After agents complete, summarize:
- Distinctive: line 166
Run early: Before creating PR, not after
- Distinctive: line 169
Re-run after fixes: Verify issues are resolved
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Comprehensive PR Review
Run a comprehensive pull request review using multiple specialized agents, each focusing on a different aspect of code quality.
Review Aspects (optional): "$ARGUMENTS"
Review Workflow:
- Load Configuration
- Read the project config file at
.specify/extensions/review/review-config.yml(if it exists). - If the file does not exist, fall back to the
defaults.agentssection in the extension'sextension.yml. - Extract the
agentsmap — each key (code,comments,tests,errors,types,simplify) is a boolean toggle. - Agents set to
falseMUST be excluded from this run. Do not launch them.
- Read the project config file at
- Determine Review Scope
- Parse arguments to see if user requested specific review aspects.
- If specific aspects were requested, run exactly those — config toggles do not apply (explicit user request overrides config).
- Default (no arguments): Run all applicable reviews that are enabled in config.
Available Review Aspects:
- comments - Analyze code comment accuracy and maintainability
- tests - Review test coverage quality and completeness
- errors - Check error handling for silent failures
- types - Analyze type design and invariants (if new types added)
- code - General code review for project guidelines
- simplify - Simplify code for clarity and maintainability
- all - Run all applicable reviews (default)
Identify Changed Files
- If the user provided a file list or explicit instructions on how to retrieve files (e.g., only staged, only unstaged, a specific folder, etc.), follow those instructions directly.
- Otherwise, you MUST execute the
.specify/scripts/bash/detect-changed-files.shwith--jsonto detect changed files. Do not attempt to detect changes by runninggitcommands directly, reading git state manually, or using any other method — always delegate to the script.- The script automatically picks the best detection mode:
- Mode A (feature branch): diffs the current branch against the default branch (
main/master) from the merge-base, plus any staged and unstaged changes. - Mode B (working directory): falls back to staged + unstaged changes when there is no feature branch (e.g., working directly on the default branch).
- Mode A (feature branch): diffs the current branch against the default branch (
- JSON output:
{"branch", "default_branch", "mode", "changed_files": [...]}
- The script automatically picks the best detection mode:
- Note: The folder containing the script may be excluded from version control or hidden by search indexing. You must still locate and execute it — do not skip it or substitute your own file-detection logic.
Determine Applicable Reviews
Based on changes and config toggles (skip any agent where
agents.<name>isfalse):- Always applicable (if enabled):
/speckit.review.code(general quality) - If test files changed (if enabled):
/speckit.review.tests - If comments/docs added (if enabled):
/speckit.review.comments - If error handling changed (if enabled):
/speckit.review.errors - If types added/modified (if enabled):
/speckit.review.types - After passing review (if enabled):
/speckit.review.simplify(polish and refine) - If an agent is disabled by config, note it in the final summary (e.g., "simplify: skipped (disabled in config)").
- Always applicable (if enabled):
Launch Review Agents
Sequential approach (one at a time):
- Easier to understand and act on
- Each report is complete before next
- Good for interactive review
Parallel approach (user can request):
- Launch all agents simultaneously
- Faster for comprehensive review
- Results come back together
Aggregate Results
After agents complete, summarize:
- Critical Issues (must fix before merge)
- Important Issues (should fix)
- Suggestions (nice to have)
- Positive Observations (what's good)
Provide Action Plan
Organize findings:
# PR Review Summary ## Critical Issues (X found) - [agent-name]: Issue description [file:line] ## Important Issues (X found) - [agent-name]: Issue description [file:line] ## Suggestions (X found) - [agent-name]: Suggestion [file:line] ## Strengths - What's well-done in this PR ## Recommended Action 1. Fix critical issues first 2. Address important issues 3. Consider suggestions 4. Re-run review after fixes
Usage Examples:
Full review (default):
/speckit.review.runSpecific aspects:
/speckit.review.run tests errors
# Reviews only test coverage and error handling
/speckit.review.run comments
# Reviews only code comments
/speckit.review.run simplify
# Simplifies code after passing reviewParallel review:
/speckit.review.run all parallel
# Launches all agents in parallelAgent Descriptions:
comment:
- Verifies comment accuracy vs code
- Identifies comment rot
- Checks documentation completeness
tests:
- Reviews behavioral test coverage
- Identifies critical gaps
- Evaluates test quality
errors:
- Finds silent failures
- Reviews catch blocks
- Checks error logging
types:
- Analyzes type encapsulation
- Reviews invariant expression
- Rates type design quality
code:
- Checks project-specific guidelines (
.specify/memory/constitution.md,CLAUDE.md,.github/copilot-instructions.md, or equivalent) compliance - Detects bugs and issues
- Reviews general code quality
simplify:
- Simplifies complex code
- Improves clarity and readability
- Applies project standards
- Preserves functionality
Tips:
- Run early: Before creating PR, not after
- Focus on changes: Agents analyze diff by default
- Address critical first: Fix high-priority issues before lower priority
- Re-run after fixes: Verify issues are resolved
- Use specific reviews: Target specific aspects when you know the concern
Notes:
- Agents run autonomously and return detailed reports
- Each agent focuses on its specialty for deep analysis
- Results are actionable with specific file:line references
- Agents use appropriate models for their complexity
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

