requesting-code-review

To automate code review requests before a git merge, you can trigger a dedicated subagent to analyze your commit range. This process identifies code quality issues and enforces production readiness best practices using a structured markdown template.

The best way to structure code review feedback is by categorizing issues into Critical, Important, and Minor levels. This approach provides clear, actionable recommendations to fix bugs and improve overall codebase health before merging changes.

A code reviewer subagent identifies changes in your development workflow by using git commands to determine the specific commit range. It then analyzes these committed changes to provide structured feedback on potential issues.

Yes, you need git commands to trigger an automated code review because the process requires commit range identification. The skill uses these git commands to locate your latest changes before dispatching the review subagent.

You should request a code review in the development workflow early and frequently, specifically after completing a new feature. Requesting reviews before merging prevents bugs and ensures adherence to project requirements.

No, you cannot use this automated code review process without a templated markdown file. The markdown template is required to provide structured review instructions and enforce best practices for code quality.