undo-recoverlisted

# Undo Recover ## Core Question What is the least destructive recovery action that preserves user work while matching whether the target is unstaged, staged, committed, pushed, untracked, stashed, or in an operation state? ## When To Use Use this skill when the user asks to: - restore or discard file changes, - unstage changes, - undo or amend local commits, - revert pushed commits, - inspect reflog or recover lost commits, - abort merge, rebase, cherry-pick, or revert, - clean untracked files, - remove sensitive or confidential files from committed history, - remove tracked but repo-excluded or local-only files from Git without deleting the working-tree file, - recover from force-push or tag/branch mistakes, - delete, replace, retag, or recover tags when routed from `tag-release`. ## When Not To Use Do not use this skill for normal branch creation/sync, conflict resolution, commit grouping, message generation, release notes, or version edits. Route to: - `branch-workflow` for normal branch switch/sync/push planning. - `resolve-conflicts` for resolving conflicts instead of aborting. - `atomic-commits` for organizing selected changes into commits. - `tag-release` for normal tag creation or tag push. ## Required Evidence Before recovery action, inspect or establish: - `git status --short --branch`, - staged and unstaged diff summaries, - untracked file list, - recent log and target commit/ref, - reflog when target or lost work is unclear, - stash list when stash is