Guide · Agent skill
How to use the Commit Message Writer agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Commit Message Writer is an agent skill that tells an AI agent to write git commit messages and pull request titles in the bracketed WARP format used by the kyegomez/swarms repository. It is aimed at contributors to that project, maintainers checking title format, and developers who want a similar bracketed style in their own work. After this guide you will know what the skill changes, how to install it, and how to ask for titles that follow it.
Commit Message Writerkyegomez/swarms · Apache-2.0 Download the skill Quick start
- 1Download the ZIP. Download the commit-messages skill ZIP from this page.
- 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for all projects, or into .claude/skills/ inside one project.
- 3Or upload it in the Claude apps. Go to Settings → Capabilities → Skills and upload the skill.
- 4Describe your change. Ask the agent for a commit message or PR title and name the function, class or file involved.
- 5Check the format. Confirm the title has a listed TYPE, a target in brackets and an imperative description.
- 6Commit yourself. Copy the title into your own git command, since the skill does not run git.
What is an agent skill and what does this one change?
An agent skill is a folder containing a SKILL.md file with instructions that an AI agent reads when it is relevant to a request. This skill's SKILL.md contains one instruction: write commit messages and pull request titles using a fixed pattern.
The pattern is [TYPE][Function/FileName][Short Description]. TYPE is one of FEAT, FIX, DOCS, REFACTOR, TEST or CHORE, written in capitals. The second bracket names the function, class, module or file the change is about. The last part is one short imperative line.
- TYPE: FEAT, FIX, DOCS, REFACTOR, TEST or CHORE
- Function/FileName: the function, class, module or file the change touches
- Short Description: one imperative line
[FIX][Agent._run][Raise AgentLLMError after retry exhaustion]
[FEAT][SkillsManager][Load skills from several directories at construction]Install the commit-messages skill
Download the ZIP of the skill from this page and unzip it. The folder must contain SKILL.md. To make it available to all your projects, unzip it into ~/.claude/skills/. To make it available only inside one project, unzip it into that project's .claude/skills/ folder.
If you use the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside your project
- Claude apps: Settings → Capabilities → Skills, then upload
How to trigger the skill with natural requests
You do not need a special command. Ask the agent for a commit message or PR title in ordinary language and mention the change. The agent should apply the bracketed format when the skill is relevant.
Name the function, class or file if you know it, because the second bracket depends on it. Describe the change in plain words and let the agent turn it into an imperative line.
- "Write a commit message for my change to the retry logic in Agent._run."
- "Draft a PR title for adding multi-directory loading to SkillsManager."
- "Suggest a commit title for the docs update in the skills README."
Examples of good output
The skill's own examples show the expected shape. Each title has a type, a target in brackets and a short instruction in the imperative mood, such as 'Raise' or 'Load'.
Check any output against the three parts before you commit. If the type is not one of the six listed, or the description is not an imperative line, ask the agent to rewrite it.
[FIX][Agent._run][Raise AgentLLMError after retry exhaustion]
[FEAT][SkillsManager][Load skills from several directories at construction]What the skill needs and what it does not do
The skill lists no requirements. It runs no scripts and uses no network access. It only changes the format of text the agent writes. It does not run git, read your diffs or touch your code, so you still need to supply the change details yourself.
The SKILL.md file is the only file. It describes the format and contains no code that reads changes.
- Requires: nothing listed
- Runs scripts: no
- Uses network: no
- Does not run git, inspect diffs or commit automatically
Tips and when to choose a different convention
This skill is built for the swarms repository's convention. If your project uses Conventional Commits or another style, the agent will still apply the swarms format unless you tell it otherwise, so either keep this skill out of that project or uninstall it there.
Keep the description short. The format asks for one imperative line, so ask for a shorter title if the agent writes a long one.
- Install per project if teammates use a different commit style
- Name the exact function or file to get a more accurate second bracket
- Review every title before committing
What people use it for
- Writing commit titles for bug fixes in the swarms repo, such as a retry error change in Agent._run
- Drafting PR titles for new features in a shared codebase
- Writing docs-only or test-only commit titles that still follow the bracketed type convention
- Teaching a team a bracketed commit style by example
Frequently asked questions
How do I install the commit-messages agent skill?
Download the ZIP from this page and unzip it so that SKILL.md sits in ~/.claude/skills/ for all projects or in .claude/skills/ inside one project. In the Claude apps, you can instead upload it under Settings → Capabilities → Skills.
What does the commit-messages skill require?
The skill lists no requirements. It runs no scripts and uses no network access. It is a single SKILL.md file with format instructions.
Is the commit-messages skill free?
The source material does not state pricing or licence terms for the skill. The project it comes from is licensed under Apache-2.0, which is listed for this item.
Does the skill commit my code or read my git diffs?
No. It only changes the format of text the agent writes. It does not run git, inspect diffs or commit anything.
Can I use this format with Conventional Commits?
Not with this skill. It applies the swarms bracketed format, so projects that use Conventional Commits should not install it, or should remove it from that project.
Why does my agent not use the bracketed format?
The skill may not be installed in the folder the agent reads, or the request may not have been clear enough to trigger it. Check the SKILL.md location and name the change and the function or file in your request.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you contribute to the swarms repository or want commit and PR titles in its bracketed WARP style. Pick a different tool or skip it if your project follows another convention, or if you want an agent that reads diffs and commits for you, since this skill only sets the title format.
Download the skill