agentleFS
jakkarin-promseejakkarin-promsee/my-harness/.claude/skills/commit-progress/SKILL.md

commit-progress

Skill1 starsChanged 4 months agoMITView on GitHub

Commit the current working-tree progress in the researcher-harness commit style — verify tests, review every change, group by concern, write a `type: summary — detail` message. Use at the end of a work session or when a coherent chunk of work is ready to be recorded.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run it anyway; it's sub-second and catches accidental code edits.

    line 14
  2. Distinctive:

    If a file was added/removed in a folder with a README.md, that README must already reflect it (note 15).

    line 22
  3. Distinctive:

    Commit on the current branch.

    line 45
  4. Distinctive:

    Never amend, rebase, or force — history here is append-only.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Commit progress — the end-of-session ritual

Turn the working tree into clean history. Written to be followable by any model: when in doubt at any step, stop and ask the owner instead of guessing.

1. Prove green first

uv run pytest -q — must pass (rule 5). Never commit red. Docs-only change? Run it anyway; it's sub-second and catches accidental code edits.

2. Read what you're committing

  • git status then git diff (and git diff --stat for the shape). Read every hunk — never commit blind, never git add -A without having read the status list.
  • Must not enter history: .env (keys), sessions/, acceptance-*.log, scratch files. If something like that shows up, it belongs in .gitignore, not the commit.
  • If a file was added/removed in a folder with a README.md, that README must already reflect it (note 15). If not, fix it now — same commit.

3. Group by concern

One commit = one concern (mirrors rule 2: one feature at a time). Unrelated changes in the tree → stage and commit them separately (git add <paths>, never all-at-once).

4. Write the message like the log

Match the precedent — check git log --oneline -5. The house format:

type: short summary — key detail or evidence
  • type ∈ feat / fix / docs / refactor / test / chore.
  • Evidence beats adjectives: "7/7 on both providers" not "works great".
  • Non-trivial change → a short body telling the story (what was the problem → what did we do → why), per doc conventions.

5. Boundaries

  • Commit on the current branch; never push unless the owner asked.
  • Never amend, rebase, or force — history here is append-only.
  • A stage/milestone completion is not this skill's job — that bookkeeping (ROADMAP, status line, README, problem.md) is the close-stage skill; run it first, then commit.

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.