agentleFS
Sign inStart free
quatico-solutionsquatico-solutions/agent-skills/skills/commit/SKILL.md

commit

Skill2 starsChanged 4 months agoMITView on GitHub

When and what to commit. Covers timing, atomic commits, and git hooks. Use when: making commits, deciding when to commit, preparing changes. Triggers: commit, commit this, commit changes, git commit, make commit, should I commit. Related: commit-notation (message formatting), handling-pull-requests (PR workflow).

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

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 5

    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:

    Before verifying the change works

    line 24
  2. Distinctive:

    Refactoring: all files affected by the structural change

    line 43
  3. Distinctive:

    Never bundle these with functional changes:

    line 49
  4. Distinctive:

    If you discover an unrelated issue while working: stash it, finish your task, commit, then fix the other issue separately.

    line 57
  5. Very specific:

    Ask: "Hooks are failing because [reason].

    line 67
  6. Distinctive:

    Use commit-notation skill for message formatting (Arlo's notation with Quatico extensions).

    line 81

“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

When to Commit

Commit when a unit of work is done and verified.

A commit marks a checkpoint where:

  • The task is complete (not "mostly done")
  • Tests pass (or you've verified manually for untested code)
  • The change works as intended

Don't commit:

  • As a save point ("I'll fix it later")
  • Incomplete work (use branches/stash instead)
  • Before verifying the change works

One Concern per Commit

Each commit should have one clear intention. Ask: "What does this commit do?" If the answer uses "and", split it.

✓ One Concern✗ Mixed Concerns
Add login endpointAdd login endpoint and fix typos
Extract helper functionRefactor and add new feature
Update dependenciesUpdate deps and fix bug they exposed
Format code (auto)Format code and change logic

What Belongs Together

A single concern often spans multiple files:

  • Feature: implementation + tests + docs for that feature
  • Bugfix: fix + regression test proving it's fixed
  • Refactoring: all files affected by the structural change

The test is: "Would reverting this commit leave the codebase in a coherent state?"

What Must Be Separate

Never bundle these with functional changes:

Change TypeWhy Separate
Formatting/lintingObscures real changes in diff
Dependency updatesSeparate risk, separate rollback
Unrelated fixesDifferent concerns, different tickets

If you discover an unrelated issue while working: stash it, finish your task, commit, then fix the other issue separately.

Git Hooks

Most projects use pre-commit hooks (often via Husky) that run linting, tests, or formatting.

When hooks fail: Fix the issue. Hooks exist to catch problems early.

Skipping hooks (--no-verify):

  • NEVER without explicit human approval
  • Ask: "Hooks are failing because [reason]. Should I skip them with --no-verify?"

Valid reasons to skip:

  • Rebasing/squashing where hooks will re-run on final commit
  • Emergency hotfix that must reach CI immediately
  • Infrastructure changes where hooks are incompatible (e.g., pre-push hook can't run without remote)

Invalid reasons:

  • "Hooks are slow"
  • "I'll fix lint errors later"
  • "Just this once"

Message Format

Use commit-notation skill for message formatting (Arlo's notation with Quatico extensions).

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