Guide Git operations with explicit authorization for history changes and destructive actions. It defines recovery snapshots before discarding work, careful handling of locks and index corruption, and checks that keep unexplained changes out of commits.
Source-control safety for Git. Two rules apply whether or not you read the body. First, never commit, amend, push, tag, rebase, cherry-pick, revert, or reset --hard unless the user asked for that exact write in this session. An explicit request to create a new commit counts anywhere in the user's own task text, but it is not a request to amend, push, or tag. Finishing a task without that request is not authorization, so leave your work uncommitted for review. Second, when a Git lock file or corrupt index blocks you, never kill the holding process or bulldoze through with deletions - wait, retry, use the holder's own stop mechanism, or stop and report. Load the body only before writing Git history or recovering Git state.
Review the instructions the agent will receive before you install.
The working tree belongs to the user. Make the change, leave it visible, and let them decide what becomes history.
The user must have asked for that exact write in this session, in their own words. An explicit request to create a new commit counts anywhere in the user's own task text, but it is not a request to amend, push, or tag. Finishing a task without that request does not authorize a history write.
commit, commit --amend, push, tag, rebase, cherry-pick, revert,
merge, branch deletion, reset --hard, path restore, and clean -f all
require an explicit ask.Recovery is insurance, not authorization. A save never expands what the user allowed you to delete or overwrite.
When the user explicitly authorized an operation that may discard or broadly overwrite workspace changes, and the workspace is an ordinary Git checkout:
After read_skill gives the physical Git skill package path, run:
bash <git-skill-dir>/scripts/workspace-recovery.sh save before-discard
Keep the printed refs/tbh/recovery/... value in your handoff, then perform
only the exact authorized operation.
If the save fails or the workspace is unsupported, stop before destruction and ask the user.
To recover that saved tree later, run:
bash <git-skill-dir>/scripts/workspace-recovery.sh restore <recovery-ref>
Restore first saves the current workspace, leaves HEAD, branch, and the real
index in place, and restores the selected snapshot into the worktree. The ref
also retains distinct staged bytes when the same path had later worktree edits.
Read those staged bytes with git show '<recovery-ref>^2:<path>'; the recovery
commit's second parent is the saved index tree. Ignored files are not saved;
restore refuses an ignored-path collision rather than overwrite data it could
not save. Use only the exact printed ref, not a revision expression.
Read-only inspection such as status, log, show, diff, blame,
branch -v, show-ref, rev-parse, for-each-ref, and merge-base is fine.
Staging named files to inspect diff --cached, and a temporary stash around a
tool that requires a clean tree, are also fine when the original state is put
back afterward.
A Git lock usually means another process is writing. Never kill the holder on your own initiative. Wait, inspect the holder read-only, use that tool's normal stop mechanism, or report the block. Never delete a lock without proving no live process owns it, and never respond to index corruption by deleting state and committing anyway.
Never commit or push while status reports changes you did not make and cannot explain.
Say so plainly and stop. Do not attempt more history surgery without direction.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create a 3D object with three.js, inspect it from every angle in an interactive viewer, and download it as OBJ + MTL or GLB for use in other 3D applications.
Maintain a private task list with deadlines, next steps, waiting parties, and blockers. Update progress and dependencies, merge duplicate items, and archive closed tasks so ongoing commitments stay clear and easy to follow.
Coordinate a task from a verifiable goal through completion. Handle work directly or split independent tasks across separate agent sessions, track progress, verify results, and arrange pull request merging when included in the goal.
Create animated HTML pages with smooth scene transitions and playback controls. An editable timeline lets users adjust scene lengths and speeds, with fixed landscape or portrait layouts prepared for video export.
Review synced Apple Health records, including steps, heart rate, sleep, and workouts. Retrieve daily summaries or detailed samples for a chosen period, and check sync status and missing data before interpreting the results.
Create and edit Word documents and templates, reorganize text, replace images, and work with tracked changes or comments. Apply proper headings and lists, then render every page to check its appearance before delivery.