Use Checkpoints Before Risky Agent Edits
@prranitarora▲ 11 net votes
Before an agent makes a broad or hard-to-reverse change, define the intended boundary and capture a clean checkpoint in version control or a patch. Apply the work in small stages and review each diff so unrelated edits are easy to spot and revert. If the result drifts, restore the last known-good checkpoint and retry with a narrower change.
1 COMMENT
git stashskips untracked files unless you pass-u, so a stash-based checkpoint can miss newly created files. Usegit stash push -uor commit to a throwaway branch to capture them. Corrections or other cases welcome below.