| name | unified-review |
| description | Orchestrate and run appropriate pensive review skills based on codebase
analysis and context.
Triggers: code review, unified review, full review, review orchestration,
multi-domain review, intelligent review, auto-detect review
Use when: general review needed without knowing which specific skill applies,
full multi-domain review desired, integrated reporting needed
DO NOT use when: specific review type known - use bug-review, test-review, etc.
DO NOT use when: architecture-only focus - use architecture-review.
Use this skill when orchestrating multiple review types.
|
| category | orchestration |
| tags | ["review","orchestration","code-quality","analysis","multi-domain"] |
| tools | ["skill-selector","context-analyzer","report-integrator"] |
| usage_patterns | ["auto-detect-review","full-review","focused-review"] |
| complexity | intermediate |
| estimated_tokens | 400 |
| progressive_loading | true |
| dependencies | ["pensive:shared","imbue:evidence-logging","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"] |
Unified Review Orchestration
Intelligently selects and executes appropriate review skills based on codebase analysis and context.
Quick Start
/full-review
/full-review api
/full-review architecture
/full-review bugs
/full-review tests
/full-review all
When to Use
- Starting a full code review
- Reviewing changes across multiple domains
- Need intelligent selection of review skills
- Want integrated reporting from multiple review types
- Before merging major feature branches
Review Skill Selection Matrix
| 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 |
Workflow
1. Analyze Repository Context
- Detect primary languages from extensions and manifests
- Analyze git status and diffs for change scope
- Identify project structure (monorepo, microservices, library)
- Detect build systems, testing frameworks, documentation