skills/git-master/SKILL.md
Git workflow expert skill: atomic commits, safe rebasing, and history archaeology (blame / bisect / pickaxe). Use this skill whenever the user wants to: commit code, split commits, generate commit messages, squash commits, rebase branches, resolve rebase conflicts, search code history, git blame, git bisect, or trace code origins. Trigger even when "git" is not explicitly mentioned — any version control, committing, rebasing, or history tracing operation should invoke this skill.
npx skillsauth add rockcookies/skills git-masterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Expert Git workflow skill covering three core capabilities. Load the corresponding reference file based on user intent and follow its workflow exactly.
| User Intent | Reference File | Signal Words |
|-------------|----------------|--------------|
| Commit code / split commits / generate commit message | references/atomic-commit.md | commit, stage, conventional commits, split commits |
| Rebase / squash history / clean up commits | references/rebase-surgeon.md | rebase, squash, fixup, force push, clean history |
| Search code history / trace changes | references/semantic-search.md | blame, bisect, who wrote, when was added, pickaxe, archaeology |
read_file to load the corresponding file from references/If intent is ambiguous, ask for clarification before loading a reference file. If multiple capabilities are needed (e.g. "commit then rebase"), load and execute them sequentially.
These rules apply to all sub-workflows and must never be violated:
git push --force — always use --force-with-leasetools
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
tools
Teach the user a new skill or concept, within this workspace.
development
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
documentation
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.