ring:requesting-code-review

To run parallel code reviews, this skill dispatches seven specialized reviewers simultaneously, covering code, business logic, security, tests, nil-safety, consequences, and dead code. This parallel process shortens feedback loops and improves delivery velocity before merging to main.

Gate 4 is the pre-merge code review phase that occurs after major feature implementation and before merging to main. You should trigger a Gate 4 code review once your feature work is complete to assess code quality and identify potential issues across multiple dimensions.

To review large pull requests effectively, this skill applies optional pre-analysis and review-slicing to divide the workload. This breaks down extensive changes into manageable segments, allowing the seven parallel reviewers to process comprehensive feedback without bottlenecking.

Yes, this parallel code review process supports standardized outputs and traceable handoffs. By delivering structured review results from all seven specialized reviewers, you can seamlessly transfer feedback to subsequent development gates and teams.

Yes, parallel code review includes dedicated security and dead-code reviewers among its seven specialized agents. This ensures that security vulnerabilities, potential consequences, and unused dead code are identified alongside standard quality and business logic checks.

While review-slicing helps manage large pull requests by distributing segments across parallel reviewers, it requires optional pre-analysis to establish context. Complex cross-file dependencies within the feature implementation might be harder to track when the review is sliced into isolated segments.