Conventional commits

Skill Elmmly/genie-team/skills/conventional-commits

Creates conventional commit messages following commitlint standards. Use when committing code, creating git commits, or when the user says commit, push, or save changes.From its SKILL.md

Install

npx -y skills add Elmmly/genie-team --skill conventional-commits

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, as published. Nobody here has run it

Conventional Commits

Generate commit messages following Conventional Commits format.

Format

type(scope): concise description (<50 chars, imperative mood)

Optional body explaining what and why (not how).

Refs: #issue or docs/backlog/item.md (if applicable)

Co-Authored-By: Claude <[email protected]>

Commit Types

Type	Use When
`feat`	New feature or capability
`fix`	Bug fix
`docs`	Documentation only
`refactor`	Code change (no feature/fix)
`test`	Adding or updating tests
`chore`	Maintenance, deps, config
`perf`	Performance improvement
`style`	Formatting (no code change)
`build`	Build system changes
`ci`	CI/CD configuration

Breaking Changes

Append ! after type/scope:

feat(api)!: remove deprecated endpoints

BREAKING CHANGE: The /v1/users endpoint has been removed.
Use /v2/users instead.

Examples

Feature:

feat(auth): add JWT token refresh endpoint

Implements automatic token refresh to prevent session expiration
during active use.

Refs: docs/backlog/P2-auth-improvements.md

Bug fix:

fix(form): prevent double submission on slow networks

Add loading state and disable button during form submission
to prevent duplicate requests.

Refactor:

refactor(utils): extract date formatting to shared module

Move duplicated date formatting logic from 5 components
into a single shared utility.

Process

Run git status to see changes
Run git diff --staged (or git diff if nothing staged)
Analyze what changed and why
Determine appropriate type from the table
Write concise description (imperative: "add" not "added")
Use HEREDOC for multi-line messages:

git commit -m "$(cat <<'EOF'
feat(scope): description

Body text here.

Co-Authored-By: Claude <[email protected]>
EOF
)"

Safety Rules

Never commit without explicit user request
Check git status before committing
Don't use --force or --no-verify
Verify staged files don't contain secrets