Skill

writing-commits

Write git commit messages following project conventions. Use when committing code, when the user says "commit", "git commit", or when preparing changes for push. Also use as reference when other skills (like creating-pull-requests) need to create commits.

npx claudepluginhub nicolaei/claude-plugins --plugin programmer

Tool Access

This skill uses the workspace's default tool permissions.

Preview

- Use conventional commit prefix: `feat:`, `fix:`, `chore:`, `refactor:`, `docs:`

SKILL.md

Similar Skills

using-superpowers

178.4k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitFeb 26, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Writing Commit Messages

Title (first line)

Use conventional commit prefix: feat:, fix:, chore:, refactor:, docs:

Describe the behaviour change in plain human language

Under 70 characters

No issue references in the title

Body

Leave a blank line after the title

If the commit relates to an issue, add Part of <issue> as the last line of the body

No Co-Authored-By trailers

No bullet lists of files changed

Format

feat: describe what changed in human language Part of org/repo#123

Examples

Good:

feat: add workflow for manually resetting the database Part of SPHF-Nettverk-IaC/noa#1009

feat: setup persistent database by removing wipe and adding migrations Part of SPHF-Nettverk-IaC/noa#1009

fix: prevent duplicate imports when seeding test data

Bad:

feat: add CI migration check job (SPHF-Nettverk-IaC/noa#1009)

(issue reference belongs in the body, not the title)

feat: update cd_pipeline.yml and deploy_app.yml to remove poststart-tasks job and add run_migrations input

(too technical, lists files instead of describing behaviour)

Rules

Write like a human, not a bot

Describe what changed from the user's perspective, not which files changed

Single-line messages are fine for small changes — only add a body when there's an issue reference or something worth explaining