requesting-code-review

Automated pre-merge code review dispatches parallel code, business-logic, and security reviewer agents simultaneously to catch design, correctness, and security issues before merge, preventing regressions and post-release defects. The system aggregates severity-classified issues and enforces implementation agent fix cycles.

Parallel reviewer orchestration dispatches code, business-logic, and security reviewer agents in a single message, aggregating their findings into a severity-classified review summary for safer merges and clear handoff to the next gate. It handles git-aware context detection automatically.

Yes, the code review workflow optionally runs CodeRabbit CLI validation with mandatory execution rules, installation guidance, and environment gating to validate changes alongside the parallel reviewer agents. This integrates seamlessly with the aggregated severity-classified review output.

Git-aware context detection auto-detects base and head SHAs, changed files, and commit summaries when inputs are omitted, allowing you to run severity-classified reviews on the current branch without manual specification. The review then dispatches three parallel reviewer agents automatically.

When reviewers find issues, the enforced fix-and-retry workflow aggregates severity-classified problems, dispatches an implementation agent to apply fixes, limits iterations, and escalates when necessary to ensure resolution. This prevents incomplete fixes from proceeding to merge.

Yes, the parallel review orchestration is applicable to pre-merge validation, feature completions, and post-bugfix checks across git branches and CI workflows, returning an aggregated review summary ready for the next gate. It auto-detects git context for each scenario.