Audit for AI-written-code anti-patterns: hallucinated APIs/symbols/imports, invented config/env keys, needless dependencies, over-engineering, ignored existing conventions/helpers. Use for AI code review, hallucination check, over-engineering or…
API contract & type-safety audit of changed code: breaking signature/route/response changes without versioning, schema drift, serialization issues, any/cast at boundaries, back-compat-breaking enum/union changes. Use for API contract review, back-compat…
Correctness audit of changed code: logic bugs, broken existing functionality, cross-file side effects, race conditions, error-path gaps, devex regressions, feature-gate leaks. Use for bug review, breakage check, side-effect tracing, devex or feature-gate leak…
One-command AI code review. Runs triage -> relevant specialist reviewers -> synthesis on the current branch and returns the verdict + report. Stack-specific signals are loaded automatically from the repo's .review-pro/ directory. Use to review a branch or PR…
Stage 3 of review-pro: dedup, weight, resolve conflicts, calibrate severity, and produce the final verdict + report from specialist findings. Use to merge reviewer results into one review verdict.
Stage 1 of review-pro: classify changed files, detect relevant specialist reviewers, detect active stacks, scope context per reviewer, and emit a dispatch plan. Use to start a review-pro review, triage a PR/branch, or fan out reviewers.
Intent audit of changed code against the originating issue or spec: requirements missing or partial, requirements implemented wrong, and behaviour nobody asked for. Use to check whether a diff does what was actually requested.
Test-quality audit of changed tests/code: weak or missing assertions, missing coverage for new behavior/branches/edge cases, flaky patterns, unrealistic test data, testing implementation details, skipped tests. Use for test review, coverage check, flakiness…