From s2s
Provides Conventional Commits patterns for writing structured, machine-readable git commit messages with types, scopes, and breaking change indicators.
How this skill is triggered — by the user, by Claude, or both
Slash command
/s2s:conventional-commitsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Conventional Commits is a specification for adding human and machine readable meaning to commit messages. This skill provides patterns for consistent, informative commit messages.
Conventional Commits is a specification for adding human and machine readable meaning to commit messages. This skill provides patterns for consistent, informative commit messages.
! or BREAKING CHANGE footer<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
| Type | When to Use | Example |
|---|---|---|
feat | New feature | feat: add user login |
fix | Bug fix | fix: resolve login timeout |
docs | Documentation only | docs: update API readme |
style | Formatting, no code change | style: fix indentation |
refactor | Code change, no feature/fix | refactor: extract auth service |
perf | Performance improvement | perf: cache user queries |
test | Adding/fixing tests | test: add login unit tests |
build | Build system changes | build: update webpack config |
ci | CI configuration | ci: add deploy workflow |
chore | Other changes | chore: update dependencies |
revert | Revert previous commit | revert: undo login changes |
Scope indicates the area of change:
feat(auth): add password reset
fix(api): handle null response
docs(readme): update installation steps
refactor(core): simplify validation logic
Common scopes:
auth, api, ui, db, coreIndicate breaking changes with ! or footer:
feat!: remove deprecated API endpoints
BREAKING CHANGE: The /v1/users endpoint has been removed.
Use /v2/users instead.
Or with footer:
feat(api): update response format
BREAKING CHANGE: Response now uses camelCase keys.
feat: add email notification on signup
feat(auth): implement OAuth2 login with Google
- Add OAuth2 flow for Google provider
- Store refresh tokens securely
- Update user model for external providers
fix(api): prevent duplicate user creation
Race condition allowed duplicate signups with same email.
Added database constraint and application-level check.
Fixes #123
feat(api)!: change authentication to JWT
Previous session-based auth replaced with stateless JWT.
All clients must update to include Bearer token.
BREAKING CHANGE: Session cookies no longer work.
Clients must use Authorization header with JWT.
Migration guide: .s2s/guides/jwt-auth.md
docs: add architecture decision records
- Create ADR template in .s2s/decisions
- Document database selection (ADR-001)
- Document API versioning (ADR-002)
| Footer | Purpose | Example |
|---|---|---|
Fixes #N | Close issue | Fixes #123 |
Refs #N | Reference issue | Refs #456 |
BREAKING CHANGE | Breaking change | See above |
Co-authored-by | Credit co-author | Co-authored-by: Name <email> |
Reviewed-by | Credit reviewer | Reviewed-by: Name <email> |
In Spec2Ship projects:
.s2s/config.yaml:
git:
commit_convention: "conventional"
feature/F{NN}-{slug}npx claudepluginhub spec2ship/spec2ship --plugin s2sGuides Git commit messages to follow Conventional Commits v1.0.0 spec, covering types (feat, fix, refactor, etc.), scopes, structure, body, footers, and examples. Use for code commits and PR reviews.
Writes, reviews, and validates git commit messages following Conventional Commits v1.0.0. Helps select types (feat/fix/etc), mark breaking changes, format multi-line commits, and map to SemVer bumps.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.