agentleFS
brayandiazcbrayandiazc/project-starter-template-en-ai/.claude/skills/commit/SKILL.md

commit

Skill2 starsChanged 2 months agoMITView on GitHub

Writes a Conventional Commits message for the staged changes and creates the commit, including the AI attribution co-author line. Use this when the user asks to commit, write a commit message, or save changes (e.g. "commit this", "make a commit for these changes"). Does not push.

187 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use act-on-feedback, generate-run-commands 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.
  • 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 4 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 4 projects that use this

  • 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

  • MindgamesSkill

    branch

    Use when a user asks to create a new local git branch and start issue work (for example, "create branch" or "start working on issue XYZ"). Use this for issue-based branch naming in the `type/scope-short-description` pattern and for always syncing local `main` from `origin/main` before creating the new branch, creating the local tracking `main` branch first when needed.

    Also in 9 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

  • 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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a well-formed commit for the current changes.

    line 6
  2. Very specific:

    Read CONTRIBUTING.md for the project's commit rules (allowed types, scope conventions, subject style, any required footers).

    line 8
  3. Distinctive:

    Keep the subject under ~72 chars.

    line 17
  4. Very specific:

    Use ! or a BREAKING CHANGE: footer for breaking changes.

    line 18
  5. Distinctive:

    Create the commit. Show the final message to the user.

    line 20
  6. Distinctive:

    Do NOT push, do NOT amend or rewrite existing history, and do NOT commit unrelated changes — keep each commit focused.

    line 24

“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

Create a well-formed commit for the current changes.

  1. Read CONTRIBUTING.md for the project's commit rules (allowed types, scope conventions, subject style, any required footers). Follow that doc over the defaults below.
  2. Inspect what is staged with git status and git diff --staged. If nothing is staged, review git diff and stage the intended files; ask before staging if it is ambiguous.
  3. Format before committing — CI requires it: if the change includes .md files, run bash .github/scripts/format.sh (Prettier) and re-stage whatever it changes; if the project already has its own [LINT_COMMAND]/formatter, run it over the touched files too.
  4. Compose a Conventional Commits message:
    • Format: <type>(<optional scope>): <short imperative subject>
    • Common types: feat, fix, docs, refactor, test, chore, build, ci.
    • Keep the subject under ~72 chars; add a body explaining the why when the change is non-trivial.
    • Use ! or a BREAKING CHANGE: footer for breaking changes.
  5. For AI-assisted work, add the attribution/co-author line in the footer as defined by CONTRIBUTING.md (a Co-Authored-By: trailer).
  6. Create the commit. Show the final message to the user.

Example subject: feat(auth): add password reset via email.

Do NOT push, do NOT amend or rewrite existing history, and do NOT commit unrelated changes — keep each commit focused.

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.