Quality

Architecture Auditor reviews the architecture a system actually executes, checking boundaries, dependencies, contracts, and ownership. Use it when auditing implemented structure or drift, not when documenting plans or diagrams.

Benchmark Comparator compares alternatives with reproducible workloads, correctness oracles, and controlled measurements. Use it when choosing between tools or implementations, not when tuning one known bottleneck.

Codebase Auditor performs broad, read-only audits of code health across security, delivery, maintainability, dependencies, diagnosability, concurrency, and lifecycle. Use it when no specialist review is the primary fit.

Delivery Reviewer reviews a completed scoped change and its affected runtime and contract paths. Use it to find change-caused defects and verify release readiness without widening scope or repairing code.

Performance Optimizer improves a measured latency, throughput, memory, CPU, or I/O problem by profiling and testing keep-or-discard changes. Use it for a known bottleneck, not for unbiased A/B comparisons.

Persistence Auditor audits queries, transactions, caches, and persistence resource lifecycles in data-heavy code paths. Use it when data correctness or scalability is at risk, not for general performance tuning.

Plan Reviewer checks an implementation plan against repository evidence and current guidance before execution. It is used for a read-only second pass to expose gaps, risks, and unsupported assumptions.

Skill Reviewer reviews standalone skills and their distribution surfaces before publication. Use it to check release readiness, contracts, and checklist compliance without changing the repository or external state.

Surgical Change Implementer delivers one approved product-code change through the smallest complete root-cause solution. Use it for scoped implementation work that needs focused editing and verification, not planning, review, or broad refactors.

Test Strategy Planner designs a read-only, risk-based test portfolio for a requested scope. Use it when you need prioritized scenarios and evidence decisions without changing code or implementing tests.

Test Suite Auditor reviews an existing test portfolio to judge what important behavior it proves, what coverage is missing, and what tests should be kept, merged, updated, or retired. Use it when test confidence or lifecycle control is uncertain.

Backend Testing Guide explains how to write unit, integration, and E2E tests for backend code. Use it when you need test coverage for services, API endpoints, database behavior, and full request flows.