agentleFS
Sign inStart free
r3bl-orgr3bl-org/r3bl-open-core/.agents/skills/create-commit-message/SKILL.md

create-commit-message

Skill486 starsChanged 15 days agoApache-2.0View on GitHub

Rules and guidelines for creating well-formatted commit messages, including 72-char limits, scope prefixes, and trailer blocks for tasks, PR closing, and attribution.

We split this skill into the rules it gives an agent

12 rules. 0 are common, 5 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When asked to create a commit message, follow these exact guidelines:

    line 8
  2. Very specific:

    Start the subject line with a scope prefix in brackets, e.g., [tui], [core], [macro].

    line 11
  3. Very specific:

    Always scan the recent git log history for the files you are modifying to determine the appropriate prefix.

    line 12
  4. Distinctive:

    Subject Line: Keep the subject line (including the scope prefix) to a maximum of 72 characters.

    line 15
  5. Distinctive:

    Tone: Use the imperative mood in the subject line (e.g., "Add feature" not "Added feature").

    line 17
  6. Distinctive:

    All trailers MUST be grouped together in a single contiguous block at the absolute end of the commit message.

    line 20
  7. Very specific:

    When a commit implements work from a task/*.md file, add a Task: trailer.

    line 26
  8. Very specific:

    Do NOT include any directory prefixes (like task/ or task/done/) in the filenames.

    line 27
  9. Very specific:

    If the commit fully resolves a GitHub Issue or PR, include Closes #XXX.

    line 34
  10. Very specific:

    If you are integrating work from another contributor (e.g., merging a community PR manually), include their attribution: Co-authored-by: …

    line 36
  11. Distinctive:

    If the user asks you to copy the commit message to the clipboard (e.g., they will handle the actual git commit step themselves), execute …

    line 53
  12. Very specific:

    Write the commit message to /tmp/commit.msg.txt using the write_to_file tool.

    line 54

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

You are an expert at writing clean, standard, and highly descriptive git commit messages. When asked to create a commit message, follow these exact guidelines:

1. Scope Prefix (Mandatory)

Start the subject line with a scope prefix in brackets, e.g., [tui], [core], [macro].

  • Always scan the recent git log history for the files you are modifying to determine the appropriate prefix. For example: git log --oneline -- <file_path> will show you what prefix is typically used for that component.

2. Formatting & Length Constraints

  • Subject Line: Keep the subject line (including the scope prefix) to a maximum of 72 characters.
  • Body: Wrap the commit message body to 72 characters per line.
  • Tone: Use the imperative mood in the subject line (e.g., "Add feature" not "Added feature").

3. Trailer Block (Footers)

All trailers MUST be grouped together in a single contiguous block at the absolute end of the commit message.

  • There must be exactly one blank line before the start of the trailer block.
  • There must be zero blank lines between the trailers themselves.

Required / Optional Trailers

  1. Task Tracking (Task:):
    • When a commit implements work from a task/*.md file, add a Task: trailer.
    • Do NOT include any directory prefixes (like task/ or task/done/) in the filenames.
    • For multiple tasks, list them on separate lines with a comma ending each line except the last.
      Task: one.md,
      two.md
  2. Issue/PR Closing (Closes):
    • If the commit fully resolves a GitHub Issue or PR, include Closes #XXX.
  3. Attribution (Co-authored-by:):
    • If you are integrating work from another contributor (e.g., merging a community PR manually), include their attribution: Co-authored-by: Name <email@example.com>.

Example

[tui] Add DECCKM tracking and refactor parser state

This commit integrates the DECCKM (Cursor Key Mode) tracking logic from
PR #470, adding the missing `cursor_key_mode` field to the terminal
state and validating it with a new conformance integration test.

Task: prepare-v0.8.0-meta-task.md,
      pty-mux-bracketed-paste.md
Closes #470
Co-authored-by: Cecile Tonglet <cecile.tonglet@cecton.com>

4. Copying to Clipboard

If the user asks you to copy the commit message to the clipboard (e.g., they will handle the actual git commit step themselves), execute these exact steps:

  1. Write the commit message to /tmp/commit.msg.txt using the write_to_file tool.
  2. Execute the following in the run_command tool: fish -c "cat /tmp/commit.msg.txt | setclip"
  3. Execute the following in the run_command tool: rm /tmp/commit.msg.txt

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