AI for QA / Scenario
Contain the Runaway Refactor
Recover from an over-broad code-agent change while preserving unrelated work and tightening the next execution boundary.
- Difficulty
- Medium
- Format
- Scenario
- Points
- 150
- Estimate
- 14 min
// MISSION BRIEF
Your Mission
An agent was asked for a test-helper rename, but its final diff is much larger than the request. Use the worktree evidence to contain the change safely, separate intended work from collateral edits, and design a bounded retry.
// FIRST CONTACT
Battle teaser
First artifact
Agent request and diff summary
What is the safest first response to this state?
- AStop further agent edits, inspect the full diff, and identify pre-existing user changes before reverting anything
- BRun a destructive hard reset that discards every uncommitted change
- CCommit all files because the requested tests passed
- DAsk the same agent to make more broad improvements before review
Answers, scoring, hints, and the full battle stay sealed.
// SKILL TAGS
ai-toolsagentic-idechange-scopescenarioai-for-qa