requesting-code-review

To request code review, you define the code range using Git and dispatch a specialized subagent to analyze the changes. The subagent identifies bugs, architectural issues, and requirement deviations, categorizing them by severity to ensure production readiness.

Automated code review identifies requirement deviations by dispatching a subagent to evaluate your code changes against the original plan and best practices. It checks for bugs and architectural flaws, categorizing feedback into Critical, Important, and Minor severities for prioritized action.

Yes, you can use Git to define the code range for an automated review. The skill supports Git integration to specify the exact commits or changes to be evaluated, allowing the specialized subagent to analyze the targeted code for bugs and architectural issues.

The best way to prioritize bugs found during a code review is to categorize feedback by severity. This skill categorizes issues into Critical, Important, and Minor levels, allowing developers to address production-readiness threats first before moving to less severe architectural issues.

You need to run an automated code review in your development workflow after completing a new feature and before merging your changes. This early analysis catches bugs, architectural flaws, and requirement deviations, preventing them from reaching production and saving debugging time.