agentleFS
radiovisualradiovisual/claude-skills/skills/piv-commit/SKILL.md

piv-commit

Skill0 starsChanged 57 days agoMITView on GitHub

Creates a new git commit for all uncommitted changes with an atomic, conventionally-tagged message. Use when work is complete and ready to be committed.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 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.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a new commit for all of our uncommitted changes.

    line 8
  2. Very specific:

    Read this project's conventions: If .claude/references/conventions.md exists, read its ## commit section and follow it — those rules win …

    line 12
  3. Very specific:

    Run git status && git diff HEAD && git status --porcelain to see what files are uncommitted.

    line 15
  4. Distinctive:

    Add the untracked and changed files.

    line 16
  5. Distinctive:

    Write an atomic commit message with an appropriate, descriptive summary.

    line 17
  6. Very specific:

    Add a tag such as feat, fix, docs, refactor, test, chore, etc.

    line 18
  7. Distinctive:

    After the commit succeeds, print two clearly labelled summaries:

    line 25
  8. Very specific:

    Only include this section if any files under .claude/ were modified or added (CLAUDE.md, .claude/references/, .claude/skills/, …

    line 31

≈ “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: Create a New Commit

Create a new commit for all of our uncommitted changes.

Process

  1. Read this project's conventions. If .claude/references/conventions.md exists, read its ## commit section and follow it — those rules win over the defaults below. That file is where a project's specifics live; this skill stays general.
  2. Run git status && git diff HEAD && git status --porcelain to see what files are uncommitted.
  3. Add the untracked and changed files.
  4. Write an atomic commit message with an appropriate, descriptive summary.
  5. Add a tag such as feat, fix, docs, refactor, test, chore, etc. that reflects our work.

Output

A single commit containing all uncommitted changes, with a conventional-commit-style message (<tag>: <atomic description>) that accurately reflects the work done.

After the commit succeeds, print two clearly labelled summaries:

What Changed

One short paragraph (3–6 sentences) describing the feature/fix/refactor that was committed — what problem it solves and what files were the key touch points. Write for a developer skimming the git log.

AI Layer Changes

Only include this section if any files under .claude/ were modified or added (CLAUDE.md, .claude/references/, .claude/skills/, .claude/agents/, etc.).

List each changed AI-layer file with a one-line note on what evolved and why. If nothing in .claude/ changed, omit this section entirely.

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.