nuke

**start over, knowingly:** the cost is counted and backed up before the reset - reports every commit, file and branch the reset would take - takes the backup itself, which is what makes the reset survivable - never resets, cleans or deletes; each of those is yours to run # Instructions ## Telemetry ```! "${CLAUDE_PLUGIN_ROOT}"/skills/nuke/nuke.sh $ARGUMENTS echo "sidecar exit: $?" ``` - `help: requested` → the run was refused before it started; `## Help` below is the whole turn - it already ran, so there is no command to issue - fail (`sidecar exit` > 0) → abort and report: "<raw terminal error>" - success (`sidecar exit` = 0) → continue to step 1 1. run the native shell command exactly as specified ```bash plugins/gitgud/skills/nuke/nuke.sh ``` - fail (`sidecar exit` > 0) → abort and report: "<raw terminal error>" - success (`sidecar exit` = 0) → continue to step 2 2. run the `=== /gitgud:nuke trigger ===` block, if the sidecar emitted one - it appears only on a dirty tree; a clean tree has nothing to back up, so skip to step 3 - run its single `git stash push` line as its own tool call, exactly as printed - the floor allows only `git stash push -u -m 'git-fresh-*'`; anything else is handed over - `-u` and not `-a` on purpose: `git clean -fd` never touches ignored files, so stashing them would collect what the reset was never going to destroy, `.env` included - non-zero exit → STOP, report the raw error, and hand over NOTHING - t...