Unslop Commit
When to Use
Use this skill when you need rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50),...
Purpose
Generate or rewrite commit messages so they read like a real engineer wrote them at the end of a real day. Conventional Commits format. Direct, specific, no template English. Why over what.
Trigger
/unslop-commit, /commit, "write a commit", "commit message", "humanize this commit", "de-slop this commit". Auto-trigger when the user has staged changes and asks for a commit message.
Rules
Subject line
- Format:
<type>(<scope>): <imperative summary>
- Scope optional. Types:
feat, fix, chore, refactor, docs, test, perf, build, ci, revert.
- Imperative mood:
add, fix, move, remove — not added, fixes, fixing.
- ≤50 chars when possible. Hard cap 72.
- No trailing period.
- Lowercase after
: unless the project capitalizes.
Body (only when subject can't carry it)
- Add for: non-obvious "why", breaking changes, migrations, security context, data integrity.
- Wrap at 72 chars. Bullets
- for two or more independent points. Single paragraph for one thought.
- End with refs:
Closes #42, Refs #17. No BREAKING CHANGE: unless truly breaking — and then write it.
Never include
- Template prefixes: "This commit...", "This change...", "We are...", "I have..."
- Marketing verbs: comprehensive, robust, enhance, leverage, seamless, holistic
- Filler adverbs: just, really, basically, simply, actually
- Restating the filename when scope already names it
- "As requested by..." (use
Co-authored-by: if you need attribution)
- AI attribution unless the project requires it
- Emoji unless project convention says so
Auto-clarity (always include body)
- Breaking changes
- Security fixes
- Data migrations
- Reverts (cite the reverted commit)
Examples
Bad → good (slop subject, no body)
- Bad:
feat: implement a comprehensive, robust solution for user profile retrieval with enhanced error handling
- Good:
feat(api): return profile fields the mobile client actually needs
Bad → good (vague body)
Bad:
fix: fixed the bug
This commit addresses an issue where the application was not working correctly
in some edge cases. We've improved the logic to handle these scenarios.
Good:
fix(checkout): ignore stale cart id from localStorage
Stale cart ids came from tabs that hadn't refreshed after a deploy. Server
now treats unknown ids as empty cart instead of 500.
Closes #842
Breaking change
feat(api)!: rename /v1/orders to /v1/customer-orders
The old route stays in place until the next major release but logs a
deprecation warning. Internal services have been migrated.
BREAKING CHANGE: third-party integrations using /v1/orders directly need
to switch to /v1/customer-orders by 2026-07-01.
Closes #1290
Boundaries
- Output the message only, in a single fenced block, ready to paste.
- Do not run
git commit, stage, or amend.
- If the change is genuinely trivial (
docs(readme): fix typo), keep it trivial. Don't pad.
- Never invent context the user didn't provide. If the "why" isn't clear, ask, or omit the body.
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
Source: sickn33/agentic-awesome-skills → skills/unslop-commit/SKILL.md
Also appears in: sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/unslop-commit/SKILL.md, sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/unslop-commit/SKILL.md
1---
2name: unslop-commit
3description: "Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop (\"comprehensive solution\", \"robust implementation\", \"leverage\", \"enhance\", \"seamlessly\", \"This commit...\"). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50),..."
4category: engineering-core
5source_repo: sickn33/agentic-awesome-skills
6source_path: "skills/unslop-commit/SKILL.md"
7source_url: https://github.com/sickn33/agentic-awesome-skills/blob/HEAD/skills/unslop-commit/SKILL.md
8metadata:
9 source: https://skillmd.com/skills/sickn33/unslop-commit
10---
11
12
13# Unslop Commit
14## When to Use
15
16Use this skill when you need rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50),...
17
18
19## Purpose
20
21Generate or rewrite commit messages so they read like a real engineer wrote them at the end of a real day. Conventional Commits format. Direct, specific, no template English. Why over what.
22
23## Trigger
24
25`/unslop-commit`, `/commit`, "write a commit", "commit message", "humanize this commit", "de-slop this commit". Auto-trigger when the user has staged changes and asks for a commit message.
26
27## Rules
28
29### Subject line
30
31- Format: `<type>(<scope>): <imperative summary>`
32- Scope optional. Types: `feat`, `fix`, `chore`, `refactor`, `docs`, `test`, `perf`, `build`, `ci`, `revert`.
33- Imperative mood: `add`, `fix`, `move`, `remove` — not `added`, `fixes`, `fixing`.
34- ≤50 chars when possible. Hard cap 72.
35- No trailing period.
36- Lowercase after `:` unless the project capitalizes.
37
38### Body (only when subject can't carry it)
39
40- Add for: non-obvious "why", breaking changes, migrations, security context, data integrity.
41- Wrap at 72 chars. Bullets `-` for two or more independent points. Single paragraph for one thought.
42- End with refs: `Closes #42`, `Refs #17`. No `BREAKING CHANGE:` unless truly breaking — and then write it.
43
44### Never include
45
46- Template prefixes: "This commit...", "This change...", "We are...", "I have..."
47- Marketing verbs: comprehensive, robust, enhance, leverage, seamless, holistic
48- Filler adverbs: just, really, basically, simply, actually
49- Restating the filename when scope already names it
50- "As requested by..." (use `Co-authored-by:` if you need attribution)
51- AI attribution unless the project requires it
52- Emoji unless project convention says so
53
54### Auto-clarity (always include body)
55
56- Breaking changes
57- Security fixes
58- Data migrations
59- Reverts (cite the reverted commit)
60
61## Examples
62
63### Bad → good (slop subject, no body)
64
65- Bad: `feat: implement a comprehensive, robust solution for user profile retrieval with enhanced error handling`
66- Good: `feat(api): return profile fields the mobile client actually needs`
67
68### Bad → good (vague body)
69
70Bad:
71```
72fix: fixed the bug
73
74This commit addresses an issue where the application was not working correctly
75in some edge cases. We've improved the logic to handle these scenarios.
76```
77
78Good:
79```
80fix(checkout): ignore stale cart id from localStorage
81
82Stale cart ids came from tabs that hadn't refreshed after a deploy. Server
83now treats unknown ids as empty cart instead of 500.
84
85Closes #842
86```
87
88### Breaking change
89
90```
91feat(api)!: rename /v1/orders to /v1/customer-orders
92
93The old route stays in place until the next major release but logs a
94deprecation warning. Internal services have been migrated.
95
96BREAKING CHANGE: third-party integrations using /v1/orders directly need
97to switch to /v1/customer-orders by 2026-07-01.
98
99Closes #1290
100```
101
102## Boundaries
103
104- Output the message only, in a single fenced block, ready to paste.
105- Do not run `git commit`, stage, or amend.
106- If the change is genuinely trivial (`docs(readme): fix typo`), keep it trivial. Don't pad.
107- Never invent context the user didn't provide. If the "why" isn't clear, ask, or omit the body.
108
109## Limitations
110
111- Use this skill only when the task clearly matches its upstream source and local project context.
112- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
113- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
114
115---
116
117**Source:** [`sickn33/agentic-awesome-skills`](https://github.com/sickn33/agentic-awesome-skills) → `skills/unslop-commit/SKILL.md`
118
119**Also appears in:** `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/unslop-commit/SKILL.md`, `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/unslop-commit/SKILL.md`