requesting-code-review

You can automate code review by dispatching a subagent to check your git diff against project standards. This skill analyzes your codebase changes and generates structured markdown feedback categorized by severity to ensure quality before merging.

Structured feedback in code quality checks categorizes identified issues into critical, important, and minor levels. This classification provides specific recommendations within a markdown report, helping developers prioritize fixes before merging feature branches.

To get a subagent to check code compliance, initiate a review request for your current changes. The subagent will analyze the git diff against your project standards and return categorized markdown feedback highlighting compliance issues.

Yes, git integration is required for automated code reviews. The process depends on git and access to your codebase to perform diff analysis, which allows the subagent to evaluate the specific changes against project standards.

The best way to review code quality for feature branches is using an automated subagent to analyze your git diff. It provides structured markdown feedback by categorizing issues into critical, important, and minor levels with actionable recommendations.

Your code review subagent requires codebase access to perform diff analysis. Without access to the repository and git history, the subagent cannot evaluate the current changes against project standards to generate accurate structured feedback.