agentleFS
Sign inStart free
catesandrewcatesandrew/skills/skills/commit-message/SKILL.md

commit-message

Skill1 starsChanged 5 days agoMITView on GitHub

Generate a conventional commit message from staged git changes and recent Codex session context, then commit with that exact message. Use when the user wants the staged changes committed with a high-signal conventional message.

62 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pr-description, changelog and 9 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

    pr-description

    Draft Nacelle PR titles, pull request descriptions, commit titles, commit descriptions, and squash commit messages. Use when asked for PR or commit wording, a branch summary, or a PR description that can be used in a commit. Omit validation sections from commit bodies and remove filler.

    Also in 9 projects that use this

  • HashiCorpSkill

    changelog

    Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.

    Also in 3 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 7 projects that use this

  • GoogleSkill

    grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

    Also in 3 projects that use this

  • OpenAISkill

    brainstorming

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

    Also in 3 projects that use this

  • +2 more from google

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 10 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 10

    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:

    Use this skill when:

    line 12
  2. Distinctive:

    Write a commit message that explains:

    line 24
  3. Distinctive:

    If there are no staged changes, stop and report that blocker instead of guessing from the working tree.

    line 33
  4. Distinctive:

    If git commit fails, return the generated message and the failure reason.

    line 34
  5. Distinctive:

    Use conventional commit format.

    line 38
  6. Distinctive:

    Use present tense and imperative mood.

    line 39
  7. Distinctive:

    If behavior changes for users, add a bullet describing the impact.

    line 44
  8. Very specific:

    Add a final Tests: ... line.

    line 45
  9. Very specific:

    Use BREAKING CHANGE: footer when applicable.

    line 46
  10. Very specific:

    If commit creation is blocked or fails, return the full generated commit message in a fenced Markdown code block with info string text, …

    line 56
  11. Distinctive:

    Prefer specificity over vague summaries.

    line 60
  12. Distinctive:

    Do not mention files unless needed for clarity.

    line 62
  13. Distinctive:

    If there is not enough evidence for a claim, omit it rather than guessing.

    line 63

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

Generate a commit message for the currently staged changes, then create the git commit with that exact message.

When to Use

Use this skill when:

  • The user asks for a commit message
  • The user asks to summarize staged changes for git commit
  • The user wants a conventional commit message from the current diff
  • The user wants the staged changes committed now
  • The task mentions staged changes and recent Codex session context

Workflow

  1. Inspect the staged diff with git and confirm there are staged changes to commit.
  2. Review recent relevant conversation context from ~/.codex/sessions when it helps explain intent or rationale.
  3. Infer the most appropriate conventional commit type such as fix, feat, refactor, docs, test, build, or chore.
  4. Write a commit message that explains:
    • what changed
    • why it changed
    • the bug fixed, if this is a bug fix
    • user-visible impact, if behavior changed
    • testing status
  5. Execute git commit using the generated message exactly as written.
  6. Report the resulting commit hash and subject line.

If there are no staged changes, stop and report that blocker instead of guessing from the working tree. If git commit fails, return the generated message and the failure reason.

Constraints

  • Use conventional commit format.
  • Use present tense and imperative mood.
  • Subject line must be 74 characters or fewer.
  • Body lines must be 80 characters or fewer.
  • Use English only.
  • The first body bullet must explain why the change was made.
  • If behavior changes for users, add a bullet describing the impact.
  • Add a final Tests: ... line.
  • Use BREAKING CHANGE: footer when applicable.
  • ASCII only. Do not use Unicode punctuation or bullets.

Output Format

On success, return:

  • the created commit hash
  • the subject line used
  • a short note that the staged changes were committed

If commit creation is blocked or fails, return the full generated commit message in a fenced Markdown code block with info string text, followed by the blocker or error.

Quality Bar

  • Prefer specificity over vague summaries.
  • Explain why more than what.
  • Do not mention files unless needed for clarity.
  • If there is not enough evidence for a claim, omit it rather than guessing.
  • The commit message used for git commit must exactly match the generated message.

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