agentleFS
Sign inStart free
UtsavBalar1231UtsavBalar1231/oh-my-claudeagent/skills/git-master/SKILL.md

git-master

Skill3 starsChanged 32 days agoMITView on GitHub

Use for all git work: splitting changes into atomic commits, rebasing and squashing, and searching history with blame, bisect and log -S. Reach for it on 'commit', 'squash', 'rebase', 'find the commit that', 'when was X added' or 'who wrote'.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ultrawork, ralplan and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • zephyrpersonalSkill

    ultrawork

    Obsessive task completion mode (Sisyphus Mode) - activates maximum intensity work with todo continuation enforcement

    Also in 4 projects that use this

  • ibahgatSkill

    ralplan

    Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.

    Also in 3 projects that use this

  • klauswgSkill

    deep-interview

    在明确批准执行之前，通过数学化歧义门控进行苏格拉底式深度访谈

    Also in 3 projects that use this

  • nicepkgSkill

    team

    根据任务快速组建临时 AI Agent 团队协作。自动从 .claude/agents/ 中选择最合适的成员组队。

    Also in 3 projects that use this

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 4 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use Bash for git operations.

    line 26
  2. Very specific:

    Use git log -S for an added or removed string, git log -G for changed matching lines, git blame for ownership, and git log --follow -- …

    line 44

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Git master

Use Bash for git operations. Match the requested operation: inspection and history search are read-only, not permission to stage, commit, rewrite, or push. Do not edit files or delegate as part of this skill. Do not commit or push unless explicitly requested.

Inspect and commit

Read status, staged and unstaged diffs, the current branch, and upstream state before mutations. Preserve unrelated work. For commits, inspect recent messages and follow the repository's style. Group each independently reviewable concern with its tests; explain why inseparable files belong together. Stage explicit paths and inspect the staged diff before committing. Verify the resulting commit and remaining working-tree state.

Rewrite safely

Before a rebase, amend, or reset, confirm the branch, account for dirty work with the user, check whether commits were pushed, and name a recovery path. Use git rebase --abort, git reset --keep ORIG_HEAD, or the reflog as appropriate. Never rewrite main/master. Rewrite pushed history only with explicit approval; an approved rewritten push uses --force-with-lease, never --force.

Stashing or discarding work is the user's step. Do not run reset --hard, checkout --, restore, clean, or stash to discard or hide changes from this shell. Stop at conflicts and report the files and next commands unless conflict resolution was requested. Do not guess resolutions.

Non-interactive commands

The shell cannot answer an editor or credential prompt. For commands that open an editor, use git -c core.editor=true; do not start an interactive editor. Keep read-only commands plain so permission rules still match. Report authentication or command failures instead of retrying blindly or claiming success.

History and evidence

Use git log -S for an added or removed string, git log -G for changed matching lines, git blame for ownership, and git log --follow -- <path> for file history. Run bisect only when requested and account for its checkout changes first.

Attach requested PR evidence through the PR upload flow. Do not commit temporary evidence images or repurpose release artifacts. Log any build, test, or lint runs with evidence_log and their real exit codes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free