code-review

Automate pull request reviews by running parallel reviewer and architect lanes that identify quality, security, and maintainability issues. This skill scopes changes using git diff, reports severity, and suggests concrete fixes with file:line references for deterministic merge gating.

Review code changes before merges by applying automated parallel assessment lanes to feature branches. The process scopes changed files via git diff, evaluates security and maintainability, and outputs structured findings with specific file:line references to gate reliable code quality.

Parallel review improves code quality evaluation by running distinct code-reviewer and architect lanes simultaneously on git diffs. This mechanism produces distinct findings on security and maintainability, ensuring comprehensive coverage and actionable recommendations with specific file:line references.

You can get specific file and line references for security issues during the code review. The skill enforces structured findings by reporting severity and suggesting concrete fixes with precise file:line references, allowing developers to quickly locate and resolve identified vulnerabilities.

Yes, this code review approach works with existing git workflows by scoping reviews directly from git diff output. It is applied to pull requests and feature branches before merges or after major feature implementations to ensure reliable code quality without disrupting your process.

You need automated structured code assessment when evaluating code changes for quality, security, and maintainability issues before merges. It is specifically applied to pull requests and feature branches after major feature implementations to enforce deterministic merge gating and ensure reliable code quality.