git-master

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.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "git-master" with this command: npx skills add rockcookies/skills/rockcookies-skills-git-master

Git Master

Expert Git workflow skill covering three core capabilities. Load the corresponding reference file based on user intent and follow its workflow exactly.

Capability Router

User IntentReference FileSignal Words
Commit code / split commits / generate commit messagereferences/atomic-commit.mdcommit, stage, conventional commits, split commits
Rebase / squash history / clean up commitsreferences/rebase-surgeon.mdrebase, squash, fixup, force push, clean history
Search code history / trace changesreferences/semantic-search.mdblame, bisect, who wrote, when was added, pickaxe, archaeology

Execution Flow

  1. Identify intent: Match user intent against the router table above
  2. Load reference file: Use read_file to load the corresponding file from references/
  3. Execute strictly: Follow every step in the reference file — never skip safety checks

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.

Universal Safety Rules

These rules apply to all sub-workflows and must never be violated:

  • NEVER rebase main/master
  • NEVER use git push --force — always use --force-with-lease
  • Before rebasing: always check for a dirty working tree
  • Before committing: confirm changes match the commit message
  • Before destructive operations: output a plan and wait for user confirmation
  • Language protocol: respond in the same language the user used

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

node-dev

No summary provided by upstream source.

Repository SourceNeeds Review
General

web-design-guidelines

No summary provided by upstream source.

Repository SourceNeeds Review
General

tsdown

No summary provided by upstream source.

Repository SourceNeeds Review