MCP CheckClaude skills for commit messages
112 public Claude skills touch on commit messages. These 50 are the closest fit, best-known sources first. Each links to its folder; copy it into ~/.claude/skills/ to use it.
commit message storyteller
Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "describe my changes", "what should…
github/awesome-copilot★ 41kMITFolder:
commit-message-storytellerconventional commit
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and…
github/awesome-copilot★ 41kMITFolder:
conventional-commitgit commit message
Write a commit message from the staged diff: a short summary line and a body explaining why.
zhuyansen/agent-skills-hub★ 478MITFolder:
git-commit-messagecodely git conventional commit
Create a git commit following the team's Conventional Commit conventions. Use when the user asks to commit changes or create a commit.
CodelyTV/agent-harness★ 296No licence statedFolder:
codely-git-conventional-commitcommit message generator
Generates standardized and meaningful commit messages following best practices. Use when writing or improving commit messages.
elisaterumi-ai/agent-skills-in-practice★ 131Apache-2.0Folder:
commit-message-generatorconventional commits
Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit this", "make commits", "clean up commits", "commit the changes". In Hedgehog, each Loop step is already meant to be its own commit —…
skyf0xx/hedgehog★ 47MITFolder:
conventional-commitscommit message
Generate a conventional commit message by analyzing staged git changes. Use when the user wants to create, write, or generate a git commit message from their current staged diff. Trigger on phrases like \"commit\", \"commit message\", \"commit msg\", \"寫…
appleboy/skills★ 23No licence statedFolder:
commit-messagegenerate commit message
Generate a commit message for staged changes
Flexonze/claude-init★ 10MITFolder:
generate-commit-messagepvc git commit message local
Writes a git commit message in PVC format. First line is `vX.Y.Z - headline`, then `- one change per line` bullets. Bumps the semantic version from the most recent commit based on diff scope (PATCH for fixes, MINOR for new functionality, MAJOR for breaking…
pro-vibe-coding/pvc-git-commit-message-local★ 4Apache-2.0Folder:
pvc-git-commit-message-localchinese commit conventions
中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。
jnMetaCode/superpowers-zh★ 8.4kMITFolder:
chinese-commit-conventionswrite
Rewrites and polishes Chinese or English prose, technical instructions, and product copy. Use when drafting, editing, localizing, or cutting AI tone. Not for code comments or commit messages.
tw93/Waza★ 7.5kMITFolder:
writegit commit
Generate well-formatted git commit messages following conventional commit standards
ThinkInAIXYZ/deepchat★ 6.4kApache-2.0Folder:
git-commitcommit ko
AI(Claude 등)가 제안한 한글 커밋 메시지의 사무적·번역투 어휘("~을 수행함", "~을 진행함", "~적 개선을 실시함" 등)를 실제 개발자가 쓰는 자연스러운 한국어 커밋 메시지로 다듬는 스킬. humanize-korean과 달리 산문 문단이 아니라 1~2줄짜리 커밋 메시지 register에 특화되어 진단·청킹 없이 단일 콜로 즉시 처리한다. 트리거 — "커밋 메시지 자연스럽게", "커밋 메시지 다듬어줘", "이 커밋 메시지 AI 티 나",…
epoko77-ai/im-not-ai★ 6.3kMITFolder:
commit-koantfu create pr
Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.
antfu/skills★ 6kMITFolder:
antfu-create-prtechnical writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
michael-denyer/pstack-claude★ 3.6kMITFolder:
technical-writingllm gate
LLM-powered quality verification using prompt hooks. Validates commit messages, code patterns, and conventions using AI before allowing operations. Use to set up intelligent guardrails.
rohitg00/pro-workflow★ 2.9kNo licence statedFolder:
llm-gatesmart commit
Run quality gates, review staged changes for issues, and create a well-crafted conventional commit. Use when saying "commit", "git commit", "save my changes", or ready to commit after making changes.
rohitg00/pro-workflow★ 2.9kNo licence statedFolder:
smart-commitwriting clearly and concisely
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
softaworks/agent-toolkit★ 2.6kMITFolder:
writing-clearly-and-conciselycommit work
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into…
softaworks/agent-toolkit★ 2.6kMITFolder:
commit-workgit integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
a5c-ai/babysitter★ 1.9kMITFolder:
git-integrationdev commit
AI DevKit · Safe git commit workflow for AI coding agents. Use when the user asks to commit, prepare a commit, stage changes, create a PR-ready checkpoint, or finish work with a conventional commit while avoiding unrelated user changes.
codeaholicguy/ai-devkit★ 1.7kApache-2.0Folder:
dev-commitunslop
Cut AI tells from text you write or edit for a human reader (commit messages, PR titles and bodies, docs, code comments, replies). Apply before committing, posting, or sending; leave prose you didn't touch alone.
michaelshimeles/rstack★ 1.4kNo licence statedFolder:
unslopoma scm
SCM (software configuration management) and Git — branching, merges, conflicts, worktrees, baselines, audit readiness, plus Conventional Commits and safe staging.
first-fluke/oh-my-agent★ 1.4kMITFolder:
oma-scmslop gate
Deterministic pre-publish scan that refuses AI-slop tells in anything about to be written, published, or sent: files, artifacts, slide titles, table headers, diagram labels, chat messages, commit messages. Use before publishing or sending any deliverable,…
huytieu/COG-second-brain★ 1.3kMITFolder:
slop-gatecommit staged
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
fcakyon/claude-codex-settings★ 1.2kApache-2.0Folder:
commit-stagedpr squash message
Generate one short Conventional Commits squash message describing only the net diff between the PR's base and head, set its header as the PR title, validate it with the repository's commitlint and both copy its description to the clipboard and display it,…
scenario-labs/skills★ 1.2kMITFolder:
pr-squash-messagecc commit msg
结构化 git commit message 生成工作流，适用于显式 commit message、提交说明或 commit-msg 场景；不负责实际执行 git commit。
doccker/cc-use-exp★ 1.1kLicence: see repoFolder:
cc-commit-msgchangelog generator
Generate changelogs and release notes from Conventional Commits with semver bump detection, Keep a Changelog formatting, and monorepo scopes. Use when preparing releases, enforcing commit standards, or automating release notes.
borghei/Claude-Skills★ 1kLicence: see repoFolder:
changelog-generatorgit pushing
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push…
mhattingpete/claude-skills-marketplace★ 689Apache-2.0Folder:
git-pushingpr description writer
Use when the user asks to write, draft, generate, or update a GitHub pull request description for the current branch. Reads the branch diff and commit messages, writes a structured PR body (summary, changes, testing), and optionally creates or updates the…
Varnan-Tech/opendirectory★ 686MITFolder:
pr-description-writernw collaboration and handoffs
Cross-agent collaboration protocols, workflow handoff patterns, and commit message formats for TDD/Mikado/refactoring workflows
nWave-ai/nWave★ 626MITFolder:
nw-collaboration-and-handoffschangelog automation
Git history'den otomatik changelog, semantic versioning, release notes, conventional commits
vibeeval/vibecosystem★ 541MITFolder:
changelog-automationmanaging git workflows
Manage Git branching strategies, commit conventions, and collaboration workflows. Use when choosing between trunk-based development, GitHub Flow, or GitFlow, implementing conventional commits for automated versioning, setting up Git hooks for quality…
ancoleman/ai-design-components★ 525MITFolder:
managing-git-workflowscommit
Helps write conventional commit messages, create atomic commits, and follow git best practices. Use when the agent needs to help with git commits, commit message writing, or git workflow guidance.
aiskillstore/marketplace★ 446No licence statedFolder:
commitgithub pr best practices
Best practices for creating GitHub pull requests including conventional commits, PR formatting, and multi-language support (en/ja). Use when creating PRs, writing PR descriptions, or formatting commit messages.
aiskillstore/marketplace★ 446No licence statedFolder:
github-pr-best-practicescommit rules
Shared commit message rules and technical constraints for skills that write commits. Not typically invoked directly.
tobihagemann/turbo★ 417MITFolder:
commit-rulesengineering change descriptions
Use when writing, rewriting, or reviewing PR/CL descriptions, commit messages, or code-change summaries that explain what changed and why. TRIGGER on "write PR description", "improve this commit message", "summarize this diff", "CL description", "change…
MiniMax-AI/mcode-stack★ 405MITFolder:
engineering-change-descriptionsgit workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers…
ericrisco/rsc-harness★ 388MITFolder:
git-workflowgenshijin commit
超圧縮コミットメッセージ生成。Conventional Commits形式で件名≤50文字、 「何を」より「なぜ」を重視。日本語・英語両対応。 「コミットメッセージ作って」「/commit」「/genshijin-commit」で起動。 ステージング変更時に自動起動候補。
InterfaceX-co-jp/genshijin★ 331MITFolder:
genshijin-commitgitflow
Branching, merging, versioning, and release conventions for the Gitflow workflow, covering main/develop branches, feature/release/hotfix branches, semantic versioning, and pull request rules. Use when creating a branch, naming a branch, planning a release…
Mindrally/skills★ 288Apache-2.0Folder:
gitflowgit commit smart
Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.
majiayu000/spellbook★ 288MITFolder:
git-commit-smartchange log generator
Automatically generates change logs from git commits, patches, and pull requests. Use when preparing software releases, creating version summaries, or maintaining CHANGELOG.md files. Analyzes commit messages (including conventional commits), diff/patch…
ArabelaTso/Skills-4-SE★ 260Apache-2.0Folder:
change-log-generatorrelease notes writer
Automatically generate user-facing release notes from git commits, pull requests, changelogs, and code changes. Use when preparing software releases, creating version announcements, documenting what changed between versions, or communicating updates to…
ArabelaTso/Skills-4-SE★ 260Apache-2.0Folder:
release-notes-writerconventional git
Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects. Use when creating branches, naming worktrees, writing commits, generating commit messages, reviewing branch conventions, or setting up…
samber/cc-skills★ 241MITFolder:
conventional-gitat commit
Generate a Conventional Commits message from staged changes and wait for confirmation before committing. Use when the user asks to commit or generate a commit message.
kairyou/agent-tools★ 183MITFolder:
at-commitblind review
Maps what a branch or the work in progress changes in behavior, before and after, from the code diff alone. Commit messages, documents, and tests stay closed, so the map shows what the code does rather than what anyone says it does. The commits are…
wellwelwel/lagune★ 174Apache-2.0Folder:
blind-reviewengineering
Authoritative engineering reference covering code conventions, comments, TypeScript type rules, testing, and commit messages. Use before writing or changing any source file, and when suggesting a commit message.
wellwelwel/lagune★ 174Apache-2.0Folder:
engineeringdeclauding
Load at the start of any task whose deliverable is prose another person will read — a PR description, commit message, README, doc, postmortem, blog post, issue or review comment, report, release note or essay — before drafting it, whether the result is…
oaustegard/claude-skills★ 157MITFolder:
declaudingrelease engineering
Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags, versioning and artifact management (SemVer, conventional commits,…
magnus919/agent-skills★ 156MITFolder:
release-engineeringcontextual commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that…
berserkdisruptors/contextual-commits★ 154MITFolder:
contextual-commit
Claude skills for commit messages: common questions
Is there a Claude skill for commit messages?
There are 112 of them, spread over 96 repositories on GitHub. Named for it and most starred: commit message storyteller (github/awesome-copilot, ★ 41k), conventional commit (github/awesome-copilot, ★ 41k) and git commit message (zhuyansen/agent-skills-hub, ★ 478). Stars rate the repository a skill sits in, not the skill.
How do I install a Claude skill for commit messages?
For commit messages, take the commit-message-storyteller folder from github/awesome-copilot (the folder that holds SKILL.md) into ~/.claude/skills/ to use it in every Claude Code project, or into .claude/skills/ for one project. In the Claude apps, zip that folder and upload it as a custom skill in settings.
Are all these commit messages skills in English?
No: 4 of those listed, such as chinese commit conventions and commit ko, are written mainly in Chinese, Japanese, Korean or Russian rather than English, though the commit messages task is the same. Claude can follow them either way, but read them before you install.
What should I check before installing a commit messages skill?
A commit messages skill is instructions Claude follows, and it can bundle scripts Claude runs, so read SKILL.md and every script first: for commit message storyteller, that is everything in the commit-message-storyteller folder. 1 of the 50 here, pvc git commit message local, come from repositories with under 10 stars, so few people have looked at it. Red flags: piping a download into a shell, sending files to a URL, and instructions to hide what it does from you.
Are these commit messages skills maintained?
68 of the 112 commit messages skills sit in repositories that changed in the 30 days before 31 Oct 2026.
Are these commit messages skills official?
No. None of the 112 commit messages skills comes from Anthropic's own skills repository, so all of them are community-made across 96 repositories.
More topics: every “Claude skills for…” page.