ac-review

You can automate code review for git diffs by running a command that inspects repository changes, surfaces regressions, and writes structured markdown reports to a designated directory without modifying source code.

Yes, after the initial review confirms scope, a separate remediation plan is generated and written as a markdown file to the project directory, providing actionable steps to fix identified issues.

Automated code review with subagents maintains a read-only orchestration process, meaning it fetches context and aggregates results without modifying your actual source code files.

The best way to review specific revisions is using a frontmatter-driven workflow that audits the changes, identifies potential improvements, and outputs both review reports and remediation plans in markdown format.

Subagent orchestration for code review works by having the main thread coordinate subagents to fetch context and run checks, aggregating results into structured markdown outputs without touching source code.

No, you do not need to manually trigger them separately; a single command audits current git changes and generates both the review report and the remediation plan sequentially after scope confirmation.