agentleFS
Sign inStart free
SentryKnown publishergetsentry/skillet/examples/commit-conventions/SKILL.md

commit-conventions

Skill13 starsChanged 7 months agoMITView on GitHub

Write disciplined git commits. Use whenever committing changes or writing commit messages — conventional-commit subjects, and never commit directly to main.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 4

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    When committing changes, follow these rules without being asked:

    line 9
  2. Very specific:

    Write every commit subject as <type>(<scope>): <description>:

    line 13
  3. Distinctive:

    Before committing, check the current branch (git branch --show-current):

    line 28
  4. Distinctive:

    Never amend, rebase, or force-push existing history unless the user explicitly asks.

    line 35
  5. Distinctive:

    Never bundle unrelated changes into one commit — mention anything you left unstaged.

    line 36

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

When committing changes, follow these rules without being asked:

Subject format

Write every commit subject as <type>(<scope>): <description>:

  • Types: feat, fix, docs, test, ref (refactor), chore. Scope is optional.
  • Imperative, present tense: "Add null check", not "Added" or "Adds".
  • At most 70 characters. No trailing period.
  • Describe the actual change, not the activity ("fix(api): Handle null user response", never "update code").

Example: after fixing a missing null check in app.js:

fix(app): Handle null result in user lookup

Branch safety

Before committing, check the current branch (git branch --show-current):

  • On main or master: create a feature branch first — git checkout -b <type>/<short-description> — then commit there. Never commit directly to main, even for small changes.
  • Already on a feature branch: commit there.

Never

  • Never amend, rebase, or force-push existing history unless the user explicitly asks.
  • Never bundle unrelated changes into one commit — mention anything you left unstaged.

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