scope-confirmed-changeslisted
Install: claude install-skill theonly1me/shadowclone
# Scope Confirmed Changes
## Use when
You fix a bug, a regression, or a review finding that you confirmed. Only a reproduction proves that a bug is real. Only the same reproduction after the fix proves that the fix works.
## Gates
1. Did you reproduce the issue before you changed code, with a test, a real command, or the real interface? If the fix already exists, a test that fails when you undo the smallest part of the fix counts as the reproduction.
2. After the fix, does the same reproduction show the expected result?
3. If you could not reproduce the issue, did you label the cause as inferred, with the data and code that support it?
4. Does each changed line serve the fix, or a test or check that the fix needs?
5. Do all checks that passed before your change still pass?
6. If an approach caused a new regression, did you remove it instead of adding a second fix on top?
## Process
Write in the user's voice. Before you write, read `~/.agents/voice.md`. If it does not exist, build it once from the user's merged pull requests, review comments, and commit messages. Use only text that the user wrote, and name those sources in your handoff. Never overwrite an existing or linked `voice.md`.
1. Write the issue as a concrete input, the wrong result, and the expected result.
2. Reproduce it in the cheapest way that shows the real symptom:
- a failing unit or integration test,
- the real command in a temporary home, or
- the real interface, such as browser or desktop au