agentleFS
edrethardoedrethardo/werkbank-board/.claude/skills/git-discipline/SKILL.md

git-discipline

Skill0 starsChanged 3 months agoMITView on GitHub

Use before starting work, after reaching any working state, at session end, and when the user asks to undo or go back — keeps every change recoverable and the history readable.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use security-audit.

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.
  • CloudflareSkill

    security-audit

    Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    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:

    Commit at every working state — "working" means the project's own checks pass, not merely that the file was saved.

    line 15
  2. Very specific:

    Never rewrite history: no reset --hard, no --amend (not even on the latest commit), no force anything.

    line 29
  3. Distinctive:

    Only when they need to care.

    line 34

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

The repo is local-only. Branches are an undo mechanism here, not a review mechanism. History is the backup — treat it that way.

Rules

  • main is the working branch; commit directly for routine work.
  • Commit at every working state — "working" means the project's own checks pass, not merely that the file was saved. Small commits beat big ones.
  • Message format: first line = what changed for the tool; body = why, when the why isn't obvious. English. Written so a future session — or a hired developer — can follow the history without asking anyone.
  • Risky or experimental work: branch first (git checkout -b try-<thing>), merge when it works. Abandoned experiment: journal it (what was tried, why abandoned — journaling skill), then delete the branch. (git branch -D — under the template's stock allowlist this shows a permission box by design; tell the user in one plain sentence what is being deleted and why before confirming.)
  • Docs, CHANGELOG and index updates go in the SAME commit as the change they describe.
  • Session end = clean tree (git status shows nothing) and a journal entry. Genuinely half-done work: commit it on a branch named wip-<thing> with a commit message starting wip: plus a journal entry saying exactly where it stands.
  • Never rewrite history: no reset --hard, no --amend (not even on the latest commit), no force anything. A wrong commit is fixed by a new commit.

Explaining git to the user

Only when they need to care. "I save a snapshot after every change, so we can always go back" covers most conversations. Never make the user run git commands.

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.