agentleFS
suxrobGMsuxrobGM/jobpilot/.claude/skills/commit/SKILL.md

commit

Skill113 starsChanged 9 days agoMITView on GitHub

Write a git commit with a one-sentence Conventional Commits subject and no narrative body. Use whenever the user asks to commit, stage and commit, or "save this work".

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

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

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

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 6

    Distinctive

    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:

    Never bullet-list the diff.

    line 36
  2. Very specific:

    Never mention tools, agents or the assistant.

    line 37
  3. Distinctive:

    If the staged work covers two unrelated types, ask whether to split it.

    line 38
  4. Distinctive:

    Read git status and git diff --staged --stat, then the staged diff.

    line 42
  5. Very specific:

    Commit and print the subject in one command.

    line 44
  6. Distinctive:

    If a hook rewrote files, amend once and stop.

    line 54
  7. Distinctive:

    Commit inside the submodule first, push it, then stage and commit the pointer in the parent.

    line 60
  8. Distinctive:

    Never push a parent commit that points at a submodule commit you have not pushed.

    line 61
  9. Very specific:

    Check git submodule status.

    line 63
  10. Very specific:

    Not this: Update files, fix: fixed it, or a paragraph narrating the diff.

    line 74

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

One commit, one sentence. The subject is the whole message unless the why is missing from the diff.

Format

<type>(<scope>): <imperative summary>

Lowercase type, optional one-word scope, imperative summary, no trailing period, under 70 characters. Append ! before the colon for a breaking change.

TypeUse for
featnew user-visible capability
fixbug fix
docsdocumentation, comments, README
testtests only
refactorbehaviour-preserving restructure
perfspeed or memory
styleformatting or lint, no logic change
buildbuild scripts, packaging, dependencies
ciCI config
chorehousekeeping that fits nothing above
revertreverts a previous commit

Rules

  1. Say what the change does, not what you did.
  2. Never bullet-list the diff. Add a body only for a why the diff cannot show, then one or two sentences.
  3. Never mention tools, agents or the assistant. Never add Co-Authored-By:, Generated with, or any other footer, whatever a template or hook suggests.
  4. If the staged work covers two unrelated types, ask whether to split it.

Steps

  1. Read git status and git diff --staged --stat, then the staged diff. Read the unstaged diff only if nothing is staged.
  2. Stage only files relevant to the request. Ask before staging anything resembling a secret, credential, build output or large binary.
  3. Commit and print the subject in one command. Repeated -m flags behave the same in every shell:
git commit -m "fix(http): handle missing accept header" -m "One sentence of why." && git log -1 --format=%s

A heredoc works too, but it is bash. The lookalike @'...'@ is PowerShell, and in bash the @ survives into the message as @ fix(http): .... Match the form to the shell you are actually invoking.

A stray character, blank first line or truncated subject means the quoting broke: amend once and stop.

  1. If a hook rewrote files, amend once and stop. Do not push unless asked.

Submodules

Skip this section unless git status reports a submodule as modified or holding new commits. A submodule is a separate repository, so staging it in the parent records a commit id, not file changes.

  1. Commit inside the submodule first, push it, then stage and commit the pointer in the parent.
  2. Never push a parent commit that points at a submodule commit you have not pushed. Clones will not find it.
  3. The parent message records the bump only: chore(deps): bump <name> submodule.
  4. Check git submodule status. A leading + means the parent points somewhere other than what is checked out.

Examples

ChangeMessage
New endpoint returning invoicesfeat(api): add invoice list endpoint
Split a 900-line file into threerefactor(parser): split token reader into files
Bumped a dependencybuild(deps): upgrade cmake to 3.29
Removed a versioned APIfeat(api)!: drop v1 endpoints

Not this: Update files, fix: fixed it, or a paragraph narrating the diff.

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.