// Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
| name | plugin-review |
| description | Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits. |
| alwaysApply | false |
| category | plugin-management |
| tags | ["review","quality","validation","testing","architecture"] |
| dependencies | ["skills-eval","hooks-eval","rules-eval"] |
| tools | ["validate_plugin.py","skill_analyzer.py"] |
| progressive_loading | true |
| model_hint | standard |
Tiered quality review of plugins with dependency-aware scoping.
| Tier | Trigger | Scope | Depth | Duration |
|---|---|---|---|---|
| branch | Default | Affected and related | Quick gates | ~2 min |
| pr | Before merge | Affected and related | Standard | ~5 min |
| release | Before version bump | All 17 plugins | Full | ~15 min |
--tier flag, find affected
plugins from git diff, resolve related plugins from
docs/plugin-dependencies.jsonAffected plugins: git diff main --name-only filtered to
plugins/*/.
Related plugins: load docs/plugin-dependencies.json,
look up each affected plugin's reverse index to find
dependents. Mark as "related" (lighter checks).
If --tier release or no git diff available, scope to
all plugins.
modules/tier-branch.mdmodules/tier-branch.md then
modules/tier-pr.mdmodules/tier-release.mdmodules/dependency-detection.md| Result | Meaning |
|---|---|
| PASS | All checks green |
| PASS-WITH-WARNINGS | Non-blocking issues |
| FAIL | Blocking issues found |
Plugin Review (<tier> tier)
Affected: <list>
Related: <list> (<reason>)
Plugin test lint type reg verdict
<name> PASS PASS PASS PASS PASS
...
Verdict: <PASS|PASS-WITH-WARNINGS|FAIL> (N/N plugins healthy)
PR and release tiers add scorecard sections.
The --quality-gate flag enables CI/CD integration with
exit codes that distinguish warnings from failures:
0: all quality gates passed1: warnings present but gates passed (non-blocking)2: quality gate failures (blocking)3: critical issues found (blocking)Use --fail-on warning to treat warnings as blocking.
Place a .plugin-review.yaml file in the plugin root
to customize thresholds and focus areas:
plugin_review:
quality_gates:
structure_min: 80
skills_min: 75
hooks_min: 70
tokens_max_total: 50000
bloat_max_percentage: 15
focus_areas:
- skills
- hooks
- tokens
exclude_patterns:
- "*/legacy/*"
- "*/deprecated/*"
severity_overrides:
missing_description: warning
large_file: info
See the /plugin-review command reference for full
usage examples.
Analyze and improve the improvement process. Use for detecting regressions and meta-optimization.
Applies client-server architecture for web/mobile apps. Use when designing systems with centralized backend services, trust boundaries, or offline-first sync.
Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.
Applies event-driven async messaging to decouple producers and consumers. Use when designing real-time or multi-subscriber systems needing loose coupling.
Applies Functional Core, Imperative Shell to isolate logic from side effects. Use when business logic is entangled with I/O or unit tests are slow and brittle.
Applies hexagonal architecture isolating domain from infrastructure. Use when designing systems where testability and port/adapter separation are priorities.