speckit.reviewer

Automate code review for git pull requests by analyzing staged changes or branch diffs against main to identify logic errors, security vulnerabilities, and maintainability issues. The process generates a categorized markdown report with severity labels, exact line references, and suggested fixes.

Static analysis in a branch diff checks for correctness flaws, security vulnerabilities, performance hotspots, and maintainability issues. It groups findings into categories like Best Practices and Style, assigning explicit severity levels and merge-blocking recommendations for critical items.

Yes, you can review specific file paths instead of the entire git diff. Scope selection allows targeting explicit file paths, staged changes, or branch comparisons against main or master to produce focused, actionable feedback for code audits.

Identify merge-blocking issues before merging by running a code review that flags CRITICAL and HIGH severity items. The review summarizes required actions and provides concrete suggested fixes or code snippets to resolve security vulnerabilities and logic errors.

The best way to format code review findings for developers is a structured markdown report. This report categorizes issues by Correctness, Security, and Performance, including descriptions, explanations of impact, exact line references, and actionable code snippets.