with one click
unified-review
// Orchestrate multiple review types into a single multi-domain review.
// Orchestrate multiple review types into a single multi-domain review.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | unified-review |
| description | Orchestrate multiple review types into a single multi-domain review. |
| alwaysApply | false |
| category | orchestration |
| tags | ["review","orchestration","code-quality","analysis","multi-domain"] |
| tools | [] |
| usage_patterns | ["auto-detect-review","full-review","focused-review"] |
| complexity | intermediate |
| model_hint | standard |
| estimated_tokens | 400 |
| progressive_loading | true |
| dependencies | ["pensive:shared","imbue:proof-of-work","imbue:structured-output"] |
| orchestrates | ["pensive:rust-review","pensive:api-review","pensive:architecture-review","pensive:bug-review","pensive:test-review","pensive:makefile-review","pensive:math-review","imbue:justify"] |
Intelligently selects and executes appropriate review skills based on codebase analysis and context.
# Auto-detect and run appropriate reviews
/full-review
# Focus on specific areas
/full-review api # API surface review
/full-review architecture # Architecture review
/full-review bugs # Bug hunting
/full-review tests # Test suite review
/full-review all # Run all applicable skills
Verification: Run pytest -v to verify tests pass.
| Codebase Pattern | Review Skills | Triggers |
|---|---|---|
Rust files (*.rs, Cargo.toml) | rust-review, bug-review, api-review | Rust project detected |
API changes (openapi.yaml, routes/) | api-review, architecture-review | Public API surfaces |
Test files (test_*.py, *_test.go) | test-review, bug-review | Test infrastructure |
| Makefile/build system | makefile-review, architecture-review | Build complexity |
| Mathematical algorithms | math-review, bug-review | Numerical computation |
| Architecture docs/ADRs | architecture-review, api-review | System design |
| General code quality | bug-review, test-review | Default review |
| Post-implementation audit | imbue:justify | High add/delete ratio, test changes, new abstractions |
# Detection logic
if has_rust_files():
schedule_skill("rust-review")
if has_api_changes():
schedule_skill("api-review")
if has_test_files():
schedule_skill("test-review")
if has_makefiles():
schedule_skill("makefile-review")
if has_math_code():
schedule_skill("math-review")
if has_architecture_changes():
schedule_skill("architecture-review")
# Default
schedule_skill("bug-review")
Verification: Run pytest -v to verify tests pass.
Dispatch selected skills concurrently via the Agent tool. Use this mapping to resolve skill names to agent types:
| Skill Name | Agent Type | Notes |
|---|---|---|
| bug-review | pensive:code-reviewer | Covers bugs, API, tests |
| api-review | pensive:code-reviewer | Same agent, API focus |
| test-review | pensive:code-reviewer | Same agent, test focus |
| architecture-review | pensive:architecture-reviewer | ADR compliance |
| rust-review | pensive:rust-auditor | Rust-specific |
| code-refinement | pensive:code-refiner | Duplication, quality |
| math-review | general-purpose | Prompt: invoke Skill(pensive:math-review) |
| makefile-review | general-purpose | Prompt: invoke Skill(pensive:makefile-review) |
| shell-review | general-purpose | Prompt: invoke Skill(pensive:shell-review) |
Rules:
pensive:math-review is NOT an agent)pensive:code-reviewer covers multiple domains, dispatch once with combined scopegeneral-purpose and instruct it to invoke the Skill toolDeferred capture for backlog findings: Findings that are triaged to the backlog (out-of-scope for the current review or deferred by the team) should be preserved so they are not lost between review cycles. For each finding assigned to the backlog, run:
python3 scripts/deferred_capture.py \
--title "<finding title>" \
--source review \
--context "Review dimension: <dimension>. <finding description>"
The <dimension> value should match the review skill that
surfaced the finding (e.g. bug-review, api-review,
architecture-review).
This runs automatically after the action plan is finalised,
without prompting the user.
Automatically selects skills based on codebase analysis.
Run specific review domains:
/full-review api → api-review only/full-review architecture → architecture-review only/full-review bugs → bug-review only/full-review tests → test-review onlyRun all applicable review skills:
/full-review all → Execute all detected skillsEach review must:
All review skills use a hub-and-spoke architecture with progressive loading:
pensive:shared: Common workflow, output templates, quality checklistsmodules/: Domain-specific details loaded on demandimbue:proof-of-work, imbue:diff-analysis/modules/risk-assessment-frameworkThis reduces token usage by 50-70% for focused reviews while maintaining full capabilities.
If the auto-detection fails to identify the correct review skills, explicitly specify the mode (e.g., /full-review rust instead of just /full-review). If integration fails, check that TodoWrite logs are accessible and that evidence files were correctly written by the individual skills.