AugmentClaude
DevOps

Commit Message Writer

By ogulcancelik· ogulcancelik/herdr· 0

Generate well-formatted Git commit messages following project conventions.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.
    Install
    Sign up to copy
    Sign up free to reveal

    This copies the whole skill folder into ~/.claude/skills/writing-commit-messages-ogulcancelik/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
    Sign up free to reveal
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Writes Git commit messages. Activates when the user asks to write a commit message, draft a commit message, or similar.

What this skill does

Writing Commit Messages

Write commit messages that follow commit style guidelines for the project.

Format

<subsystem>: <summary>

<reference issues/PRs/etc.>

<long form description>

Rules

Subject line

  • Subsystem prefix: Use a short, lowercase identifier for the area of code changed (e.g., terminal, vt, lib, config, font). Determine this from the file paths in the diff. If changes span the macOS app, use macos. For GTK, use gtk. For build system, use build. Use nested subsystems with / when helpful and exclusive (e.g., terminal/osc).
  • Summary: Lowercase start (not capitalized), imperative mood, no trailing period. Keep it concise—ideally under 60 characters total for the whole subject line.

References

  • If the change relates to a GitHub issue, PR, or discussion, list the relevant numbers on their own lines after the subject, separated by a blank line. E.g. #1234
  • If there are no references, omit this section entirely (no blank line).

Long form description

  • Describe what changed, what the previous behavior was, and how the new behavior works at a high level.
  • Use plain prose, not bullet points. Wrap lines at ~72 characters.
  • Focus on the why and how rather than restating the diff.
  • Keep the tone direct and technical without no filler phrases.
  • Don't exceed a handful of paragraphs; less is more.

Workflow

  • If .jj is present, use jj instead of git for all commands.
  • Run a diff to see what changes are present since the last commit.
  • Identify the subsystem from the changed file paths.
  • Identify any referenced issues/PRs from the diff context or branch name.
  • Draft the commit message following the format above.
  • Apply the commit
  • Don't push the commit; leave that to the user.

Related skills

N

n8n Architect

EtienneLescot

Create, edit, and validate n8n workflows and automation configurations.

D

Deploy to Vercel

vercel-labs

Deploy your app to Vercel with preview or production environments.

V

Vercel CLI with Tokens

vercel-labs

Deploy and manage Vercel projects using token-based authentication instead of interactive login.

U

Understand Diff

Egonex-AI

Analyze git diffs and pull requests to understand changes, affected components, and risks.