speckit-review

You can review a PR by running /speckit.review, which detects changed files and runs specialized agents sequentially or in parallel based on your configuration. It analyzes code quality, comments, tests, error handling, and types to produce an aggregated issue summary.

Change-aware code review works by detecting changed files via a dedicated bash script and selectively running analysis agents based on configured toggles. It scrutinizes modified modules and new logic to catch quality issues early before merging.

Yes, you can customize which agents run by setting toggles in the review configuration file at .specify/extensions/review/review-config.yml with fallback to extension.yml. The system respects these toggles unless explicitly overridden by user-requested aspects.

The best way is to use a multi-aspect review that consolidates findings from specialized agents into critical, important, and suggestion categories. This produces an aggregated issue summary with a fix-first action plan for error handling and type design.

Yes, spec-kit code reviews require a specific project structure to read optional review configuration and execute changed-file detection. The system looks for config in .specify/extensions/review/review-config.yml with fallback to extension.yml, and uses scripts in .specify/scripts/bash/.

Code simplification suggestions are prioritized through an aggregated summary that categorizes findings into critical, important, and suggestion tiers, providing a recommended action plan to address the most impactful issues first.