Enforces native git commands for moving, renaming, and deleting tracked files.
npx skills add https://github.com/ab300819/keel-workflow --skill git-safety-ab300819
Please help me install this Agent Skill. Skill: git-safety Source: https://github.com/ab300819/keel-workflow/tree/main/skills/git-safety Command: npx skills add https://github.com/ab300819/keel-workflow --skill git-safety-ab300819
mv or rm on Git-tracked files, Git loses the file history and records the change as a delete-plus-add, polluting the index and breaking traceability. This Skill prevents that by mandating native Git commands for all file operations on tracked files. ## Core Features & Use Cases - Safe Move & Rename: Requires git mv instead of mv so Git preserves file history during refactors. - Safe Delete: Requires git rm instead of rm so deletions are staged in the index immediately. - Pre-operation Self-check: Instructs the agent to run git ls-files <path> first, then choose git mv/git rm for tracked files or plain mv/rm for untracked ones. - Use Case: During a codebase restructure, the agent checks each file's tracking status before moving it, ensuring the Git history of every relocated module stays intact. ## Quick Start Before moving or deleting any file in this repository, check its tracking status with git ls-files and use git mv or git rm for tracked files.High-intent search queries and answers about installing and using this skill.
Use git mv <old_path> <new_path> instead of the plain mv command. Git then tracks the rename natively and preserves the file's commit history rather than recording a delete plus a new file.
Use git rm <path> or git rm -r <path> for directories. This removes the file from both the working tree and the index in one step, avoiding unstaged deletion leftovers that plain rm would cause.
Run git ls-files <path>. If it returns the path, the file is tracked and you should use git mv or git rm; if it returns nothing, the file is untracked and plain mv or rm is safe.
This happens when the file was moved with the plain mv command instead of git mv. Git then treats the operation as a deletion and a new untracked file, which breaks history continuity for that path.
Run git status before any large-scale move or cleanup operation to confirm the working tree is clean. A dirty tree makes it harder to review the structural changes and increases the risk of mixing unrelated modifications.
inspedralbesInitialize a Git repository and create an initial commit.
tomholfordStage, commit, and push changes to a Git repository.
g-zenrRemove dead code, unused imports, and stale configuration files.
cstrahanAutomate programmatic interactive rebases for git history cleanup and commit hygiene.