Skip to content

grijalva10/oc-seller-finder / .claude/skills/undo

Safely undo changes or go back to an earlier version of the code. Use when Steve says undo, go back, revert, "it was working before", or "I broke it".

Undo safely

First ask Steve what he wants to undo. Then run git status and git log --oneline -10 to see where things stand, and explain it in plain words.

Pick the safe option:

  • Changes to one file that are not saved yet (not committed): git restore <file>. This throws away those edits, so ask Steve first.
  • The last save (commit) was bad: run git revert HEAD, then git push. This adds a new save that undoes the old one. Nothing is lost.
  • An older save: find it with git log --oneline, then run git revert <id>.
  • Settings only: change settings.toml back by hand.

Never use git reset --hard, git checkout -- ., git clean or a force push. They delete work for good.

Undo never touches data/ (the homes, statuses and notes), because git does not save it. To undo a home's status, run uv run python -m sellers mark <id> <status>.

After the undo, run uv run pytest and show Steve that things work again.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall