How do I install the Git Conventional Commits skill?

Run npx skillmds@latest add majiayu000/git-conventional-commits-2 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 Git Conventional Commits 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 Git 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 Git Conventional Commits free to use?

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

Who published Git Conventional Commits?

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

Git Conventional Commits by majiayu000

Name: Git Conventional Commits
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

When to Use

Apply when writing commit messages to maintain consistent, readable git history that enables automated changelog generation.

Patterns

Pattern 1: Commit Format

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

[optional body]

[optional footer(s)]

Source: https://www.conventionalcommits.org/en/v1.0.0/

Pattern 2: Types

feat:     New feature (MINOR version bump)
fix:      Bug fix (PATCH version bump)
docs:     Documentation only
style:    Formatting, no code change
refactor: Code change, no feature/fix
perf:     Performance improvement
test:     Adding/fixing tests
chore:    Build, tooling, deps
ci:       CI/CD changes

Pattern 3: Examples

# Feature
feat(auth): add OAuth2 login with Google

# Bug fix
fix(cart): prevent negative quantity values

# Breaking change (triggers MAJOR version)
feat(api)!: change response format to JSON:API

BREAKING CHANGE: All endpoints now return JSON:API format.
Migration guide: docs/migration-v2.md

# With scope
fix(ui/button): correct hover state color

# Multi-line body
feat(search): add full-text search

Implements Elasticsearch integration for product search.
Includes fuzzy matching and relevance scoring.

Closes #123

Pattern 4: Scope Guidelines

Scope = module, component, or area affected

Good scopes:
- auth, cart, api, db
- ui/button, api/users
- deps, config, ci

No scope when change is broad:
- docs: update README
- chore: update dependencies

Anti-Patterns

Vague messages - "fix bug", "update code", "WIP"
Missing type - Always prefix with type
Too long subject - Keep under 72 chars
Multiple changes - One logical change per commit

Verification Checklist

Type prefix present (feat/fix/docs/etc.)
Subject is imperative ("add" not "added")
Subject under 72 characters
Breaking changes marked with ! or footer
One logical change per commit

MonoPilot: Module Scopes

Module scopes (11 modules):
  settings, technical, planning, production, warehouse,
  quality, shipping, npd, finance, oee, integrations

Cross-cutting scopes:
  rls, auth, lp-system, api, ui, db, deps

Examples:
  feat(warehouse): add LP receiving form
  fix(planning): correct BOM snapshot on WO creation
  feat(rls): add org_id policy for quality_checks table
  fix(auth): handle expired session redirect

---name: git-conventional-commits-2description: Apply when writing commit messages to maintain consistent, readable git history that enables automated changelog generation.---## When to UseApply when writing commit messages to maintain consistent, readable git history that enables automated changelog generation.## Patterns### Pattern 1: Commit Format```<type>(<scope>): <subject>[optional body][optional footer(s)]```Source: https://www.conventionalcommits.org/en/v1.0.0/### Pattern 2: Types```feat: New feature (MINOR version bump)fix: Bug fix (PATCH version bump)docs: Documentation onlystyle: Formatting, no code changerefactor: Code change, no feature/fixperf: Performance improvementtest: Adding/fixing testschore: Build, tooling, depsci: CI/CD changes```### Pattern 3: Examples```bash# Featurefeat(auth): add OAuth2 login with Google# Bug fixfix(cart): prevent negative quantity values# Breaking change (triggers MAJOR version)feat(api)!: change response format to JSON:APIBREAKING CHANGE: All endpoints now return JSON:API format.Migration guide: docs/migration-v2.md# With scopefix(ui/button): correct hover state color# Multi-line bodyfeat(search): add full-text searchImplements Elasticsearch integration for product search.Includes fuzzy matching and relevance scoring.Closes #123```### Pattern 4: Scope Guidelines```Scope = module, component, or area affectedGood scopes:- auth, cart, api, db- ui/button, api/users- deps, config, ciNo scope when change is broad:- docs: update README- chore: update dependencies```## Anti-Patterns- **Vague messages** - "fix bug", "update code", "WIP"- **Missing type** - Always prefix with type- **Too long subject** - Keep under 72 chars- **Multiple changes** - One logical change per commit## Verification Checklist- [ ] Type prefix present (feat/fix/docs/etc.)- [ ] Subject is imperative ("add" not "added")- [ ] Subject under 72 characters- [ ] Breaking changes marked with `!` or footer- [ ] One logical change per commit## MonoPilot: Module Scopes```Module scopes (11 modules): settings, technical, planning, production, warehouse, quality, shipping, npd, finance, oee, integrationsCross-cutting scopes: rls, auth, lp-system, api, ui, db, depsExamples: feat(warehouse): add LP receiving form fix(planning): correct BOM snapshot on WO creation feat(rls): add org_id policy for quality_checks table fix(auth): handle expired session redirect```

Frequently asked questions

Git Conventional Commits