# Conventional Commit

> Write a Conventional Commits message for the currently staged changes.

- Skill: `staffinityai/conventional-commit` (Agent Skill)
- Install (CLI): `npx skillmds@latest add staffinityai/conventional-commit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/staffinityai/conventional-commit/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: StaffinityAI (https://skillmd.com/u/staffinityai)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/staffinityai/conventional-commit

---


# Conventional commit

A standalone, command-style skill — no MCP server involved. It shows the pattern
of a skill you trigger explicitly with `/conventional-commit` rather than one
Claude picks on its own (`disable-model-invocation: true`).

## Steps

1. Inspect what is staged: run `git diff --cached` (and `git status` for context).
   - If nothing is staged, tell the user to `git add` first and stop.
2. Decide the **type** from the change: `feat`, `fix`, `docs`, `refactor`,
   `test`, `chore`, `perf`, `build`, `ci`, or `style`.
3. Pick an optional **scope** (the affected area, e.g. `mcp_advanced`).
4. Write the message:

   ```
   <type>(<scope>): <imperative summary, <=50 chars, no trailing period>

   <optional body: why the change was made, wrapped at ~72 cols>
   ```

   Add a `BREAKING CHANGE:` footer if the change is incompatible.
5. Present the message in a fenced block. Do **not** run `git commit` unless the
   user explicitly asks you to.

## Example

```
feat(mcp_advanced): add search_notes tool

Lets clients find notes by substring instead of only listing all of
them, mirroring the create/read pair already exposed.
```