How do I install the Commit Writer skill?

Run npx skillmds@latest add uitbreidenos/commit-writer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Commit Writer safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Commit Writer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Commit Writer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Commit Writer?

UitbreidenOS (@uitbreidenos) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commit Writer by uitbreidenos — Agent Skill

Name: Commit Writer
Rating: 4.2 (5 reviews)
Author: UitbreidenOS

File contents

Commit Writer Skill

When to activate

You have staged changes and need a well-structured commit message
Writing commit messages across a team that uses Conventional Commits
Generating commit messages that will feed into automated changelogs
You want Claude to analyse the diff and propose the right commit type

When NOT to use

Work in progress / draft commits — use git commit -m "wip" and squash later
Merge commits — let git generate these
Revert commits — git revert generates the message automatically

Instructions

Conventional Commits format

<type>(<scope>): <subject>

[body]

[footer]

Types:

Type	When to use
`feat`	New feature or capability visible to users
`fix`	Bug fix
`docs`	Documentation only — no code change
`style`	Formatting, whitespace — no logic change
`refactor`	Code restructuring with no behaviour change
`perf`	Performance improvement
`test`	Adding or fixing tests
`chore`	Build, tooling, dependency updates
`ci`	CI/CD configuration changes
`revert`	Reverts a previous commit

Rules:

Subject: imperative mood, lowercase, no full stop, max 72 chars — "add user auth" not "Added user auth"
Scope: optional, in parentheses — the module, package, or file area affected
Body: explain why, not what (the diff shows the what)
Breaking changes: add BREAKING CHANGE: in the footer, or ! after the type (feat!:)

Workflow

Run this before invoking the skill:

git diff --staged   # see what you're about to commit

Then prompt Claude:

Write a conventional commit message for these staged changes:

[paste git diff --staged output, or describe what changed]

Claude will:

Identify the primary change type
Infer the scope from files changed
Draft a subject line (imperative, ≤72 chars)
Add a body if the change needs explanation
Flag breaking changes if present

Multi-change commits

If the diff contains multiple logical changes, Claude will either:

Write one commit that covers the primary change (mentioning others in the body)
Suggest splitting into separate commits with git add -p

Output format

Claude outputs the commit message ready to copy-paste:

git commit -m "feat(auth): add JWT refresh token rotation

Implement sliding session windows by rotating refresh tokens on each use.
Previous tokens are invalidated immediately after rotation.

Closes #234"

Example

Staged diff includes:

src/auth/tokens.py — new rotate_refresh_token() function
tests/test_tokens.py — tests for the new function
CHANGELOG.md — updated

Expected output:

feat(auth): add refresh token rotation

Rotate refresh tokens on each use to implement sliding session windows.
Previous tokens are invalidated immediately, reducing the window for
token theft after a session is compromised.

Closes #234

---name: commit-writerdescription: Write conventional commit messages from staged diff — type, scope, subject, body, breaking changes---# Commit Writer Skill## When to activate- You have staged changes and need a well-structured commit message- Writing commit messages across a team that uses Conventional Commits- Generating commit messages that will feed into automated changelogs- You want Claude to analyse the diff and propose the right commit type## When NOT to use- Work in progress / draft commits — use `git commit -m "wip"` and squash later- Merge commits — let git generate these- Revert commits — `git revert` generates the message automatically## Instructions### Conventional Commits format```<type>(<scope>): <subject>[body][footer]```**Types:**| Type | When to use ||------|-------------|| `feat` | New feature or capability visible to users || `fix` | Bug fix || `docs` | Documentation only — no code change || `style` | Formatting, whitespace — no logic change || `refactor` | Code restructuring with no behaviour change || `perf` | Performance improvement || `test` | Adding or fixing tests || `chore` | Build, tooling, dependency updates || `ci` | CI/CD configuration changes || `revert` | Reverts a previous commit |**Rules:**- Subject: imperative mood, lowercase, no full stop, max 72 chars — "add user auth" not "Added user auth"- Scope: optional, in parentheses — the module, package, or file area affected- Body: explain *why*, not *what* (the diff shows the what)- Breaking changes: add `BREAKING CHANGE:` in the footer, or `!` after the type (`feat!:`)### WorkflowRun this before invoking the skill:```bashgit diff --staged # see what you're about to commit```Then prompt Claude:```Write a conventional commit message for these staged changes:[paste git diff --staged output, or describe what changed]```Claude will:1. Identify the primary change type2. Infer the scope from files changed3. Draft a subject line (imperative, ≤72 chars)4. Add a body if the change needs explanation5. Flag breaking changes if present### Multi-change commitsIf the diff contains multiple logical changes, Claude will either:- Write one commit that covers the primary change (mentioning others in the body)- Suggest splitting into separate commits with `git add -p`### Output formatClaude outputs the commit message ready to copy-paste:```bashgit commit -m "feat(auth): add JWT refresh token rotationImplement sliding session windows by rotating refresh tokens on each use.Previous tokens are invalidated immediately after rotation.Closes #234"```## Example**Staged diff includes:**- `src/auth/tokens.py` — new `rotate_refresh_token()` function- `tests/test_tokens.py` — tests for the new function- `CHANGELOG.md` — updated**Expected output:**```feat(auth): add refresh token rotationRotate refresh tokens on each use to implement sliding session windows.Previous tokens are invalidated immediately, reducing the window fortoken theft after a session is compromised.Closes #234```---

Frequently asked questions

Commit Writer