SkillsAdd

smithery.ai

drafting-conventional-commits

Draft a Conventional Commits message from either a short summary of changes or by inspecting the local git diff. Use when the user wants a commit message formatted as type(scope): subject, with optional body and footers for breaking changes or issue references.

First seen Apr 19, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

conventional-commit Similar name
github/awesome-copilot

Prompt and workflow for generating conventional commit messages using a structured XML format. …

16.1K installs
conventional-git Similar name
samber/cc-skills

Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for Gi…

2.1K installs
conventional-commit Similar name
marcelorodrigo/agent-skills

Create conventional commit messages following best conventions. Use when committing code change…

939 installs
conventional-commit-message Similar name
conventional-changelog/conventional-changelog

Generate high-quality Conventional Commit messages for repositories using conventional-changelo…

14 installs
conventional-commits Similar name
patricio0312rev/skills

Generates semantic commit messages following the Conventional Commits specification with proper…

418 installs
conventional-commit Similar name
ilteoood/harness

Prompt and workflow for generating conventional commit messages using a structured XML format. …

364 installs

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,533 B
  • docs SUMMARY.md 298 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Conventional Commit Drafter

Overview

Turn a short change summary into a Conventional Commits message. If the user asks you to infer changes, inspect the local git diff. Ask only for missing essentials like type, scope, or breaking change details.

Workflow

  1. If the user provides a summary, read it. If they ask you to check changes, inspect git status -sb and git diff --stat, then open specific diffs as needed.
  2. Infer a commit type.
  3. Identify an optional scope (subsystem, module, or area). Omit if unclear.
  4. Draft a concise subject in imperative mood, lower-case, no trailing period.
  5. Include a brief body that explains the reason for the change (why, not how). If the reason is not clear from the summary or diff, ask the user for it.
  6. Add footers for breaking changes or issue references.

Conventional Commits Rules

  • Format: type(scope): subject
  • Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
  • Subject: imperative, lower-case, no period, <= 72 chars when possible
  • Breaking change: add ! after type/scope and include BREAKING CHANGE: <details> footer
  • Issue refs: include Refs: #123 or Closes: #123 footer when provided

Type Selection Heuristics

  • New user-facing behavior: feat
  • Bug fix: fix
  • Docs only: docs
  • Formatting (no behavior change): style
  • Refactor without behavior change: refactor
  • Performance improvement: perf
  • Tests only: test
  • Build system/deps: build
  • CI config/pipeline: ci
  • Maintenance chores: chore
  • Revert of a prior commit: revert

Output

Return only the commit message, with no extra commentary. If you need the reason for the change, ask a short follow-up question instead of returning a commit message.

Examples

Input summary: "add pagination to the invoices list" Output:

feat(invoices): add pagination to list

Input summary: "fix crash when opening empty cart; breaking API change: remove legacy cart token" Output:

fix(cart)!: prevent crash on empty cart

BREAKING CHANGE: remove legacy cart token

Input summary: "update readme with setup steps" Output:

docs(readme): add setup steps