skills/commit-messages/SKILL.md
Generate clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or preparing releases.
npx skillsauth add thedecipherist/claude-code-mastery commit-messagesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate consistent, informative commit messages following the Conventional Commits specification.
git commit commandgit diff --staged to see what's being committed<type>(<scope>): <description>
[optional body]
[optional footer(s)]
| Type | Description | Example |
|------|-------------|---------|
| feat | New feature | feat(auth): add OAuth2 login |
| fix | Bug fix | fix(api): handle null response |
| docs | Documentation only | docs(readme): add setup instructions |
| style | Formatting, no code change | style: fix indentation |
| refactor | Code change, no new feature/fix | refactor(db): extract query builder |
| perf | Performance improvement | perf(search): add result caching |
| test | Adding/fixing tests | test(auth): add login unit tests |
| build | Build system changes | build: update webpack config |
| ci | CI configuration | ci: add GitHub Actions workflow |
| chore | Maintenance tasks | chore(deps): update dependencies |
| revert | Revert previous commit | revert: feat(auth): add OAuth2 |
The scope should be a noun describing the section of the codebase:
auth, api, db, ui, configsearch, checkout, dashboardBREAKING CHANGE: for breaking changesFixes #123 to close issuesRefs #456 to reference without closingfeat(search): add fuzzy matching support
Implement Levenshtein distance algorithm for typo tolerance
in search queries. Configurable via FUZZY_THRESHOLD env var.
fix(cart): prevent duplicate items on rapid clicks
Add debounce to add-to-cart button and check for existing
items before insertion.
Fixes #234
feat(api)!: change response format to JSON:API
BREAKING CHANGE: API responses now follow JSON:API spec.
All clients need to update their parsers.
- Wrap data in `data` object
- Move metadata to `meta` object
- Add `links` for pagination
refactor(auth): consolidate authentication logic
- Extract JWT handling to dedicated service
- Move session management from controller to middleware
- Add refresh token rotation
This prepares for the upcoming OAuth2 integration.
When generating a commit message:
development
Audit code and dependencies for security vulnerabilities. Use when reviewing PRs, checking dependencies, preparing for deployment, or when user mentions security, vulnerabilities, or audit.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------