Gum validate-code-changes
Validate all code changes on the current branch. Spawns QA and refactoring agents in parallel to review for correctness, edge cases, code quality, and pattern adherence. Use when ready to review branch changes before merging.
install
source · Clone the upstream repo
git clone https://github.com/vchelaru/Gum
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/vchelaru/Gum "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/validate-code-changes" ~/.claude/skills/vchelaru-gum-validate-code-changes && rm -rf "$T"
manifest:
.claude/skills/validate-code-changes/SKILL.mdsource content
Invoking product-manager agent for this task.
You are coordinating a code validation review for the current branch. Your job is to spawn the qa and refactoring-specialist agents in parallel to validate all changes on this branch.
Steps
-
Identify changes: Run
to see which files changed, thengit diff main...HEAD --stat
for the full diff. Also rungit diff main...HEAD
to see the commit history.git log main..HEAD --oneline -
Spawn agents in parallel: Launch both agents using the Task tool concurrently:
-
qa agent (
): Review all changes on this branch for correctness, edge cases, regressions, and potential bugs. Look at the git diff against main to understand what changed and validate the implementation.subagent_type: qa -
refactoring-specialist agent (
): Review all changes on this branch for code quality, structure, naming, duplication, and adherence to project patterns. Look at the git diff against main to understand what changed and suggest improvements.subagent_type: refactoring-specialist
-
-
Summarize findings: After both agents complete, compile a consolidated report with:
- QA findings: Bugs, edge cases, risks (high/medium/low)
- Refactoring findings: Code smells, structural improvements, pattern violations
- Recommended actions: Prioritized list of changes to make before merging
Context for this request
$ARGUMENTS