How do I install the Conventional Commits skill?

Run npx skillmds@latest add claude-code-community-ireland/conventional-commits 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 Conventional Commits 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 Conventional Commits?

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 Conventional Commits free to use?

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

Who published Conventional Commits?

Claude-Code-Community-Ireland (@claude-code-community-ireland) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Conventional Commits by claude-code-community-ireland

Name: Conventional Commits
Rating: 4.2 (5 reviews)
Author: Claude-Code-Community-Ireland

Conventional Commits

Generate well-formatted conventional commit messages from staged changes. Use when the user asks to commit changes, write a commit message, or follows the conventional commits standard.

File contents

Conventional Commits Skill

Generate well-formatted conventional commit messages from staged changes.

Instructions

When asked to commit changes or when the user runs /commit:

Analyze staged changes using git diff --staged
Identify the type of change:
- feat: New feature
- fix: Bug fix
- docs: Documentation only
- style: Formatting, no code change
- refactor: Code restructuring
- test: Adding/updating tests
- chore: Maintenance tasks
Determine the scope (optional): The part of codebase affected

Write the message following this format:

<type>(<scope>): <short description>

<body - what and why, not how>

<footer - breaking changes, issue refs>

Examples

Simple feature:

feat(auth): add password reset functionality

Bug fix with body:

fix(api): handle null response from external service

The weather API occasionally returns null during maintenance windows.
Added defensive check to prevent crash and return cached data instead.

Breaking change:

feat(db)!: migrate from MySQL to PostgreSQL

BREAKING CHANGE: Database connection strings must be updated.
See migration guide in docs/migration-v2.md

Rules

Keep the first line under 72 characters
Use imperative mood ("add" not "added")
Don't end with a period
Reference issues when applicable
Add ! after type for breaking changes

Frequently asked questions