agentleFS
Sign inStart free
nc9nc9/skills/commit/SKILL.md

commit

Skill4 starsChanged 54 days agoMITView on GitHub

Pre-commit workflow - project quality gates, submodules, issue refs, atomic commits. Use when user says "commit", "/commit", or wants to commit changes.

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

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

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run in order. Stop on failure.

    line 22
  2. Very specific:

    Run format, lint, typecheck, test — always preferring project-defined scripts over hardcoded tooling.

    line 33
  3. Very specific:

    Put them in the message body, never the title: Closes: BACKEND-4ZW when the commit closes the issue, Refs: BACKEND-4ZW for related work.

    line 66
  4. Very specific:

    When one file's hunks belong in different commits, split them with git add -p or git apply --cached per ~/.claude/CLAUDE.md — never …

    line 72

“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

Adds the owner's gates on top of Claude Code's built-in commit behaviour: run the project's own quality gates, commit submodules first, carry issue refs into the message body.

Message convention (type(scope): message + the type table) lives in ~/.claude/CLAUDE.md, which is always loaded — follow it there, don't restate it.

When to Use

User says "commit" / "/commit", or work on a feature or fix just finished.

Workflow

Run in order. Stop on failure.

1. Submodules

git submodule status. For each submodule with changes: enter it, run this same workflow (gates → commit) inside it, return to the parent, then git add <submodule-path> to stage the pointer update. The parent commit lands after its submodules do.

2. Quality gates

Run format, lint, typecheck, test — always preferring project-defined scripts over hardcoded tooling. Hardcoding bunx biome or bunx tsc runs the wrong tool in an oxlint/oxfmt/tsgo/eslint repo: it either finds nothing or emits confusing errors. The project's own scripts encode its real toolchain; trust them.

Detection order per gate — first that exists wins:

  1. Task-runner target — composite make check / make ci first, then per-gate make format|lint|typecheck|test; same for a justfile or Taskfile.yml. Probe without running: make -n <target> 2>/dev/null.
  2. package.json scripts — composite first (check:strict, check, ci), then per-gate (format, lint, typecheck, test). Probe with jq -e '.scripts.<name>' package.json; run via bun run.
  3. pyproject.toml — the repo's own task alias if it has one, else uv run pytest.
  4. Language defaults, only when nothing above exists — TS: bunx biome lint --write ., bunx biome format --write ., bunx tsc --noEmit. Python: uv run ruff check --fix ., uv run ruff format ., uv run ty check . (fallback uv run basedpyright .), uv run pytest.

A composite target covers all four gates — running it means the per-gate steps can be skipped. If a gate has no script and no language default (e.g. a Go-only repo), skip it with a note rather than inventing a command. If lint or format mutated files, re-stage before committing.

3. Issue references

Scan the conversation for:

  • Linear — PROJ-123, BACKEND-4ZW (uppercase prefix + alphanumeric id)
  • GitHub — #123, org/repo#123, or an issue URL
  • Sentry — an issue URL or short issue id

Put them in the message body, never the title: Closes: BACKEND-4ZW when the commit closes the issue, Refs: BACKEND-4ZW for related work.

4. Atomic commits

One commit per feature or fix, covering only what this conversation touched. When one file's hunks belong in different commits, split them with git add -p or git apply --cached per ~/.claude/CLAUDE.md — never edit-revert-edit the working tree to isolate a hunk.

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