agentleFS
Sign inStart free
MovGP0MovGP0/Skills/git/SKILL.md

git

Skill1 starsChanged 4 months agoMITView on GitHub

Local Git operations skill based on the user's Obsidian Git notes. Use when Codex needs to help with Git configuration, commits, branches, merging, rebasing, fixup commits, amending commits, splitting commits, stash, bisect, worktrees, tags, logs, reflog, refs, LFS, Scalar, git-tfs, submodules, subtrees, SSH setup, credential helpers, or Git troubleshooting workflows.

We split this skill into the rules it gives an agent

9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for practical Git tasks and troubleshooting.

    line 10
  2. Very specific:

    When the task involves a destructive or history-changing operation such as reset --hard, branch deletion, force pushes, or broad cleanup, …

    line 12
  3. Distinctive:

    Read only the reference file needed for the current task:

    line 16
  4. Distinctive:

    Use git status --short --branch or a similarly focused inspection command before changing repository state.

    line 28
  5. Distinctive:

    Prefer scoped, reversible operations over broad cleanup.

    line 30
  6. Distinctive:

    Do not run destructive commands just because a note lists them as examples.

    line 31
  7. Distinctive:

    Treat examples that contain private names, email addresses, IP addresses, domains, or credentials as placeholders to be replaced with …

    line 32
  8. Distinctive:

    After making Git configuration or repository changes, validate with the narrowest useful command:

    line 39
  9. Distinctive:

    Use only the commands relevant to the task.

    line 47

“Common” is measured: kept by at least 6 in 10 of the 49 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

Overview

Use this skill for practical Git tasks and troubleshooting. Start from the repository state and the exact command, branch, commit, remote, or error the user mentions. Prefer focused commands that inspect the current state before changing anything.

When the task involves a destructive or history-changing operation such as reset --hard, branch deletion, force pushes, or broad cleanup, inspect state first and make the risk explicit before acting.

Reference Routing

Read only the reference file needed for the current task:

  • references/configuration.md: git config, identity, aliases, editor/diff/merge tool setup, credential helpers, self-signed certificate handling, and recommended config values.
  • references/daily-workflows.md: branches, commits, stash, bisect, worktrees, tags, remote pruning, revert/reset, Git notes, and basic ref migration.
  • references/branching-merging-rebasing.md: branch management, merge choices, conflict handling, rebasing, autosquash fixups, amend, split commits, reorder/drop commits, and force-with-lease guidance.
  • references/history-and-inspection.md: git log, pickaxe/grep history search, changed-file history analysis, show-ref, reflog, and fsck.
  • references/large-repos-and-extensions.md: Git LFS, Scalar/Microsoft Git, VFS for Git, and git-tfs.
  • references/submodules-and-subtrees.md: choosing between submodules and subtrees plus add/update/push commands.
  • references/ssh-setup.md: SSH agent setup, key creation, host compatibility settings, public-key registration, and SSH clone reminders.

Operating Rules

  • Use git status --short --branch or a similarly focused inspection command before changing repository state.
  • Preserve the user's exact branch, path, remote, commit hash, and ref names.
  • Prefer scoped, reversible operations over broad cleanup.
  • Do not run destructive commands just because a note lists them as examples.
  • Treat examples that contain private names, email addresses, IP addresses, domains, or credentials as placeholders to be replaced with task-specific values.
  • For Git LFS setup, avoid overwriting existing hooks blindly. If hooks already exist, inspect them and use the manual update flow when needed.
  • For self-signed certificate problems, avoid globally disabling TLS verification. Prefer host-scoped configuration or Git Credential Manager certificate configuration.
  • For large repositories, consider Scalar before older VFS for Git; the notes identify VFS for Git as superseded.

Validation

After making Git configuration or repository changes, validate with the narrowest useful command:

git status --short --branch
git config --list --show-origin
git log --oneline --decorate -5

Use only the commands relevant to the task; do not dump large logs unless the user asks for them.

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