Commit Messages
- 93 installs
- 325 repo stars
- Updated August 2, 2026
- athola/claude-night-market
Generate conventional commit messages from staged diffs when you are ready to commit but want consistent feat/fix/docs formatting.
About
Commit messages is an agent skill from the Claude Night Market collection that turns staged git changes into conventional commit messages suited for solo repos and small teams. It defines a repeatable ritual: pull status and cached diff in parallel, optionally enrich with sem entity names instead of raw hunk guessing, classify type and scope, then draft an imperative subject plus wrapped body and footers. That saves time when you ship fast with Claude Code or Cursor and do not want vague subjects like "fix stuff". It is intentionally not full PR preparation— the SKILL.md directs you to sanctum:pr-prep for that—and not for amend workflows you should do directly in git. Complexity is beginner-friendly with an estimated ~350 token footprint and fast model hint. Use whenever you have staged changes and need a message; it spans Build daily work and Ship review moments when commits must read clearly in changelog automation.
- Parallel git context gather: status, cached stat/diff, recent log—stops if nothing staged
- Optional sem diff --staged --json for entity-level subjects when sem is available
- 10 conventional types: feat, fix, docs, refactor, test, chore, style, perf, ci
- Subject line cap 50 chars; body wrapped at 72 with optional BREAKING CHANGE footer
- Explicit handoff: full PR prep belongs in sanctum:pr-prep, not this skill
Commit Messages by the numbers
- 93 all-time installs (skills.sh)
- Ranked #238 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/athola/claude-night-market --skill commit-messagesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 93 |
|---|---|
| repo stars | ★ 325 |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 2, 2026 |
| Repository | athola/claude-night-market ↗ |
What it does
Generate conventional commit messages from staged diffs when you are ready to commit but want consistent feat/fix/docs formatting.
Files
Conventional Commit Workflow
When To Use
- Generating conventional commit messages from staged changes
When NOT To Use
- Full PR preparation: use sanctum:pr-prep
- Amending existing commits: use git directly
Steps
1. Gather context (run in parallel):
git status -sbgit diff --cached --statgit diff --cachedgit log --oneline -5- When sem is available (see
leyline:sem-integration):
sem diff --staged --json for entity-level changes
If nothing is staged, tell the user and stop.
When sem output is available, use entity names (function, class, method) in the commit subject and body instead of parsing raw diff hunks. For example, "add function validate_webhook_url" instead of "add validation logic to notify.py".
2. Classify: Pick type (feat, fix, docs, refactor, test, chore, style, perf, ci) and optional scope.
3. Draft the message:
- Subject:
<type>(<scope>): <imperative summary>(50 chars max) - Body: What and why, wrapped at 72 chars
- Footer: BREAKING CHANGE or issue refs
4. Slop check: reject these words and replace with plain alternatives:
| Reject | Use instead |
|---|---|
| leverage, utilize | use |
| seamless | smooth |
| comprehensive | complete |
| robust | solid |
| facilitate | enable |
| streamline | simplify |
| optimize | improve |
| delve | explore |
| multifaceted | varied |
| pivotal | key |
| intricate | detailed |
Also reject: "it's worth noting", "at its core", "in essence", "a testament to"
4a. Character-level slop check: load shared/output-hygiene.md (Contract A) and strip these markers. Inline fallback if that module is absent:
| Marker | Replace with |
|---|---|
"+" as a prose conjunction | and (keep + in versions/code) |
em-dash — | colon, period, comma, or rewrite |
-- as prose punctuation | colon or rewrite |
arrows -> / → as connectors | to / into |
smart quotes “ ” ‘ ’ | straight " and ' |
4b. Subject-matter check (Contract B): describe the change by its reader-facing effect. Name neither the AI origin nor the specific marker removed. Do NOT write remove AI slop, de-slop, AI-generated content, AI phrasing, replace em-dashes, or remove smart quotes. Test: if the subject only makes sense as "I cleaned up AI output", rewrite it. For example docs: clarify the setup section, not style: replace em-dashes with colons.
5. Write to ./commit_msg.txt and preview.
Rules
- NEVER use
git commit --no-verifyor-n - Write for humans, not to impress
- If pre-commit hooks fail, fix the issues
Exit Criteria
- [ ]
commit_msg.txtwritten to the working directory containing
the drafted conventional commit message
- [ ] Subject line follows
<type>(<scope>): <summary>format and
is at most 50 characters
- [ ] Slop word check passes: none of the banned words (leverage,
utilize, seamless, comprehensive, robust, etc.) appear in the message
- [ ] Character-level check passes: no em-dashes, no
+as prose
conjunction, no smart quotes, no -> as prose connector
- [ ] If nothing is staged, skill halts immediately and reports
"nothing staged" without producing a commit message
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148FAQ
Is Commit Messages safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.