MCPInstall

writing-commit-messages

Write clear, conventional commit messages with proper type prefixes, scopes, and body content.

Installs
457
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill writing-commit-messages
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads writing-commit-messages automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Writing Commit Messages

Write commit messages that are useful for humans and machines.

Format

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

<optional body>

<optional footer>

Subject Line Rules

  • 50 characters or less for the subject
  • Use imperative mood: "add feature" not "added feature" or "adding feature"
  • Don't capitalize the first letter after the type prefix
  • No period at the end

Types

TypeWhen to use
featNew user-facing feature
fixBug fix
refactorCode restructuring without behavior change
docsDocumentation changes
testAdding or updating tests
choreBuild, CI, tooling, deps
perfPerformance improvement
styleFormatting, whitespace (not CSS)
ciCI/CD pipeline changes
revertReverting a previous commit

Scope (Optional)

The area of the codebase affected:

  • feat(auth): add OAuth2 login flow
  • fix(api): handle null response from payments endpoint
  • refactor(db): extract query builder into module

Body (When Needed)

Explain why, not what (the diff shows what):

fix(checkout): prevent duplicate order submissions

The submit button was not disabled after the first click,
allowing users to create multiple orders. This caused
duplicate charges in Stripe.

Footer (When Needed)

BREAKING CHANGE: rename `getUserById` to `findUser`

Closes #456
Co-authored-by: Name <email>

Examples

Good:

feat(dashboard): add real-time notification bell
fix: resolve race condition in WebSocket reconnect
refactor(api): consolidate error handling middleware
test: add integration tests for payment webhook
chore: upgrade TypeScript to 5.4

Bad:

fixed stuff
WIP
update
changes
asdf

When to Commit

  • Each commit should represent one logical change
  • Don't mix refactoring with feature work in the same commit
  • Don't commit half-working code (use git stash instead)
  • Commit early and often on feature branches, squash before merge if needed

Breaking Changes

If the commit introduces a breaking change:

  1. Add ! after the type: feat(api)!: change auth token format
  2. Add BREAKING CHANGE: in the footer with migration instructions

FAQ

What does the writing-commit-messages skill do?

Write clear, conventional commit messages with proper type prefixes, scopes, and body content.

How do I install writing-commit-messages?

Run npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill writing-commit-messages in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/writing-commit-messages/ (personal) or .claude/skills/writing-commit-messages/ (project).

Which AI agents can use writing-commit-messages?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is writing-commit-messages safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains writing-commit-messages?

It is published by spencerpauly in spencerpauly/awesome-cursor-skills. It has 457 recorded installs.

More from spencerpauly/awesome-cursor-skills

View all →

visual-qa-testing

spencerpauly/awesome-cursor-skills

Visually QA a web application by launching it in Cursor's built-in browser, taking screenshots, checking console errors, and auditing network requests. Use after making UI changes to verify they look correct.

Testing & QA648 installs

auditing-security

spencerpauly/awesome-cursor-skills

Perform a systematic security audit of a codebase, checking for OWASP Top 10 vulnerabilities, secrets exposure, and insecure patterns.

Security598 installs

responsive-testing

spencerpauly/awesome-cursor-skills

Open the app in Cursor's browser at multiple viewport sizes, screenshot each, and report any layout breakage.

Testing & QA569 installs

suggesting-cursor-rules

spencerpauly/awesome-cursor-skills

When the user repeats the same correction or convention multiple times, suggest a Cursor rule to encode it permanently.

559 installs

systematic-debugging

spencerpauly/awesome-cursor-skills

Structured debugging methodology — reproduce, isolate, hypothesize, verify. Covers git bisect, binary search, logging, and minimal reproduction.

grinding-until-pass

spencerpauly/awesome-cursor-skills

Keep iterating on code changes until the tests pass, the build succeeds, or linting is clean. Runs in a tight loop of fix → run → check → repeat. Use when you want the agent to autonomously grind through test failures or build errors.

Testing & QA551 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.