How do I install the Conventional Commit skill?

Run npx skillmds add majiayu000/conventional-commit-4 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 Commit safe to use?

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

Which AI agents work with Conventional Commit?

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

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

Who published Conventional Commit?

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

Conventional Commit by majiayu000 — Agent Skill

Name: Conventional Commit
Rating: 4.2 (5 reviews)
Author: majiayu000

Conventional Commit

Generates commit messages following Conventional Commits 1.0.0 specification. Use when committing changes, staging files, creating commits, or when user says "commit", "git commit", or asks for a commit message.

majiayu000 ba8ee7e 2 files · 2.8 KB Updated Sep 9, 2026 567 repo stars

File contents

Conventional Commit Generator

Generate commit messages following Conventional Commits 1.0.0.

Workflow

Run git status and git diff HEAD to analyze changes
Stage files: user-specified only, or git add -A for all
Determine type and scope from changes
Generate commit message incorporating user hints
Commit: git commit -m "subject" -m "body" -m "footer"
Output: <hash> <subject>

Scope Boundaries

DO: Analyze git changes, generate messages, stage files, commit

DO NOT: Modify code, push (unless asked), create branches, amend without request

Commit Format

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

<body>

<footer>

Type Selection

Change	Type
Bug fix	`fix`
New/changed feature	`feat`
Performance	`perf`
Restructuring	`refactor`
Formatting	`style`
Tests	`test`
Documentation	`docs`
Build/deps	`build`
CI/CD	`ci`
DevOps	`ops`
Other	`chore`

Subject Line (max 72 chars)

Format: type(scope): description or type: description
Imperative mood: "add" not "added"
Lowercase first letter, no trailing period

Breaking Changes

Add ! before colon: feat(api)!: remove endpoint

Footer: BREAKING CHANGE: description

Examples

feat: add email notifications on new messages

fix(cart): prevent ordering empty shopping cart

feat(api)!: remove status endpoint

BREAKING CHANGE: /api/status removed, use /api/health instead.
Refs: JIRA-1337

Anti-patterns

Avoid: "update", "fix bug", "changes", "WIP", capitalized first letter, trailing period, past tense

---name: conventional-commit-4description: Generates commit messages following Conventional Commits 1.0.0 specification. Use when committing changes, staging files, creating commits, or when user says "commit", "git commit", or asks for a commit message.--- # Conventional Commit Generator Generate commit messages following [Conventional Commits 1.0.0](https://www.conventionalcommits.org/). ## Workflow 1. Run `git status` and `git diff HEAD` to analyze changes 2. Stage files: user-specified only, or `git add -A` for all 3. Determine type and scope from changes 4. Generate commit message incorporating user hints 5. Commit: `git commit -m "subject" -m "body" -m "footer"` 6. Output: `<hash> <subject>` ## Scope Boundaries **DO:** Analyze git changes, generate messages, stage files, commit **DO NOT:** Modify code, push (unless asked), create branches, amend without request ## Commit Format ``` <type>(<scope>)<!>: <description> <body> <footer> ``` ## Type Selection | Change | Type | |--------|------| | Bug fix | `fix` | | New/changed feature | `feat` | | Performance | `perf` | | Restructuring | `refactor` | | Formatting | `style` | | Tests | `test` | | Documentation | `docs` | | Build/deps | `build` | | CI/CD | `ci` | | DevOps | `ops` | | Other | `chore` | ## Subject Line (max 72 chars) - Format: `type(scope): description` or `type: description` - Imperative mood: "add" not "added" - Lowercase first letter, no trailing period ## Breaking Changes Add `!` before colon: `feat(api)!: remove endpoint` Footer: `BREAKING CHANGE: description` ## Examples ``` feat: add email notifications on new messages ``` ``` fix(cart): prevent ordering empty shopping cart ``` ``` feat(api)!: remove status endpoint BREAKING CHANGE: /api/status removed, use /api/health instead. Refs: JIRA-1337 ``` ## Anti-patterns Avoid: "update", "fix bug", "changes", "WIP", capitalized first letter, trailing period, past tense

Frequently asked questions