semantic-commits
Standardizes git commit messages using the Conventional Commits format to document change intent clearly.
Install
mkdir -p .claude/skills/semantic-commits && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10479" && unzip -o skill.zip -d .claude/skills/semantic-commits && rm skill.zipInstalls to .claude/skills/semantic-commits
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Write descriptive conventional commit messages that explain intent. USE FOR: committing changes; reviewing staged diffs; drafting commit messages; when the user asks to commit. DO NOT USE FOR: general coding; writing tests; deployment.Key capabilities
- →Draft commit messages
- →Explain intent
- →Enforce conventional commits
- →Use scopes
How it works
It guides the user to write descriptive commit messages that explain the 'why' behind changes, following conventional commit formats.
Inputs & outputs
When to use semantic-commits
- →Committing new features
- →Documenting bug fixes
- →Refactoring commit history
- →Writing clear commit messages
About semantic-commits
Guides the user in drafting commit messages that describe the 'why' rather than the 'what.' It enforces specific types, scopes, and formatting rules.
>-
When not to use it
- →General coding
- →Deployment
Prerequisites
Limitations
- →72-character subject limit
- →Requires descriptive intent
How it compares
It mandates a focus on intent over mechanics, ensuring the git history is a communicative record.
Compared to similar skills
semantic-commits side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| semantic-commits (this skill) | 0 | 8mo | Review | Beginner |
| openspec-archive-change | 4 | 9mo | Review | Intermediate |
| session-wrap | 1 | 10mo | Review | Intermediate |
| tbd | 0 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
openspec-archive-change
studyzy
归档实验性工作流中已完成的变更。当用户想要在实现完成后最终确定并归档变更时使用。
session-wrap
team-attention
This skill should be used when the user asks to "wrap up session", "end session", "session wrap", "/wrap", "document learnings", "what should I commit", or wants to analyze completed work before ending a coding session.
tbd
jlevy
|-
preserve
markwharton
Preserve the most recently approved plan to docs/plans/
release-closeout-engineer
ThiagoGuislotti
Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is ready.
session-handoff
Maximumsoft-Co-LTD
Serialize mid-session context into a handoff doc so the next session (or engineer) can resume without cold-start