stash-shelvelisted

# Stash Shelve ## Core Question How should temporary work be safely shelved, restored, or inspected without losing user changes or staged boundaries? ## When To Use Use this skill when: - the user asks to stash, shelve, apply stash, pop stash, list stash, or inspect stash - dirty work blocks sync or branch switch - temporary preservation is needed before another Git action - the user asks to include or exclude untracked files from a stash ## When Not To Use Do not use this skill when: - permanent undo/recovery after destructive action - normal commit instead of temporary shelf - conflict resolution after stash apply - cleaning untracked files Route to: - destructive recovery routes to `undo-recover` - stash apply conflicts route to `resolve-conflicts` - commit instead of stash routes to `atomic-commits` - branch sync after stash routes to `sync-branch` ## Required Evidence Before action, inspect or establish: - status with staged/unstaged/untracked groups - stash list and stash show evidence - whether staged boundary must be preserved - untracked inclusion request - target stash reference - conflict state after apply No-evidence rule: - Do not make strong claims without observed evidence. - State assumptions when proceeding under incomplete evidence. - Stop when missing evidence affects safety, correctness, user work, remote state, or irreversible action. ## Operating Contract You MAY: - inspect relevant repository state and project files. - generate a plan,