agentleFS
Sign inStart free
diriendirien/yet-another-agent-harness/.claude/skills/commit/SKILL.md

commit

Skill19 starsChanged 8 months agoMITView on GitHub

Atomic, semantic-boundary git commit workflow

  • Reads credentials

188 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use validate-plan, act-on-feedback and 10 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.
  • shawn-dumasSkill

    validate-plan

    Validate an orchestration plan after pre-flight certification. Runs adversarial review, deep review (verify prompt data against codebase), and PoC gate for risky approaches. Auto-invoked by orchestrate-* skills at Step 8.

    Also in 5 projects that use this

  • MicrosoftSkill

    act-on-feedback

    Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

    Also in 3 projects that use this

  • decocmsSkill

    add-mcp-tools

    Guide for adding new MCP tools with consistent patterns for schemas, tool definitions, registry updates, and Better Auth integration

    Also in 3 projects that use this

  • MicrosoftSkill

    generate-run-commands

    Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

    Also in 3 projects that use this

  • mitsuhikoSkill

    oebb-scotty

    Austrian rail travel planner (ÖBB Scotty). Use when planning train journeys in Austria, checking departures/arrivals at stations, or looking for service disruptions. Covers ÖBB trains, S-Bahn, regional trains, and connections to neighboring countries.

    Also in 3 projects that use this

  • mitsuhikoSkill

    pi-share

    Load and parse session transcripts from shittycodingagent.ai/buildwithpi.ai/buildwithpi.com/pi.dev (pi-share) URLs. Fetches gists, decodes embedded session data, and extracts conversation history.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 11 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 11

    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:

    When the user runs /commit or asks to commit changes.

    line 9
  2. Distinctive:

    Run git status and git diff --staged to understand what's changed

    line 13
  3. Distinctive:

    If nothing is staged, identify logical change groups and stage them separately

    line 14
  4. Distinctive:

    Write a commit message following Conventional Commits:

    line 15
  5. Distinctive:

    Use the imperative mood in the subject line

    line 22
  6. Distinctive:

    Keep subject under 72 characters

    line 23
  7. Distinctive:

    Add body with "why" not "what" if the change isn't self-evident

    line 24
  8. Distinctive:

    Create the commit using a heredoc for the message

    line 25
  9. Distinctive:

    Run git status to verify

    line 26
  10. Very specific:

    NEVER use --no-verify or --amend unless explicitly asked

    line 29
  11. Distinctive:

    NEVER stage .env, credentials, or secret files

    line 30
  12. Distinctive:

    Prefer multiple small commits over one large commit

    line 31

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

/commit — Atomic Commit Workflow

When to use

When the user runs /commit or asks to commit changes.

Steps

  1. Run git status and git diff --staged to understand what's changed
  2. If nothing is staged, identify logical change groups and stage them separately
  3. Write a commit message following Conventional Commits:
    • feat: new feature
    • fix: bug fix
    • refactor: code restructuring
    • docs: documentation
    • test: tests
    • chore: tooling/build
  4. Use the imperative mood in the subject line
  5. Keep subject under 72 characters
  6. Add body with "why" not "what" if the change isn't self-evident
  7. Create the commit using a heredoc for the message
  8. Run git status to verify

Rules

  • NEVER use --no-verify or --amend unless explicitly asked
  • NEVER stage .env, credentials, or secret files
  • Prefer multiple small commits over one large commit
  • Each commit should compile and pass tests independently

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