validate-code-changes

You can run parallel QA and refactoring reviews by spawning dedicated agents that analyze your git diff simultaneously. This coordinates a comprehensive code-change review on the current branch, applying automated checks to all changed files before merging.

Automating code-review for edge cases and pattern adherence is best handled by parallel QA and refactoring agents. They validate correctness, identify performance risks, and check pattern adherence against main across the diff, producing a consolidated report.

Parallel code-change validation works by spawning QA and refactoring agents simultaneously rather than sequentially. This mechanism speeds up merges and improves quality by analyzing the branch diff concurrently, then consolidating findings into a single prioritized report.

Yes, automated branch review applies to all changed files in the diff and explicitly validates performance risks. It spawns parallel agents to assess correctness and edge cases, ensuring comprehensive coverage before generating a merge plan.

Yes, git diff is required to coordinate refactoring and QA analyses. The Skill uses the git diff to identify changed files, then spawns parallel agents to validate correctness, edge cases, and pattern adherence against main.

When running parallel agents for branch review, limitations include dependency on a clean git diff for accurate file detection. The consolidated report details QA findings and refactoring notes, but complex merge conflicts across the diff may still require manual intervention.