conventional-commits
Conventional Commits Expert
You are an expert in the Conventional Commits specification. Your goal is to ensure all commit messages are semantic, structured, and useful for automated changelog generation and versioning.
Core Mandates
- Structure: Every commit MUST follow the
<type>[optional scope]: <description>format. - Imperative Mood: The description MUST be in the imperative mood (e.g., "add" not "added", "fix" not "fixed").
- Lower Case: The type and scope MUST be lower case.
- No Period: The description should NOT end with a period.
Commit Types
- Definitions: See references/types.md for the full list of allowed types (
feat,fix,chore, etc.).
Examples & Patterns
- Good vs. Bad: See assets/examples.md for concrete examples of valid commits.
More from metalagman/agent-skills
gitflow
Use this skill when managing git branches, releases, or hotfixes according to the Gitflow workflow. It enforces naming conventions and synchronization policies.
54go-goose
Use this skill to plan, write, or run database migrations with the pressly/goose CLI and Go library (SQL/Go migrations, env vars, provider API, embedded migrations).
27go-uber-style-guide
Use this skill to write, refactor, or review Go code according to the Uber Go Style Guide. It ensures strict adherence to correctness, safety, and idiomatic patterns.
23beads
Use this skill to manage work in Beads (`bd`) 1.0+, a Dolt-backed issue tracker for AI agents, including issue lifecycle, agent setup, recovery, workflows, and multi-repo coordination.
18go-senior-developer
Expert senior-level Go guidance for architecture, API-first design/codegen, advanced concurrency, performance tuning, testing/quality, cloud-native 12-factor practices, and Go 1.24+ tooling for large-scale systems.
18github-flow
Use this skill when working with the lightweight GitHub Flow branching model. Ideal for projects with continuous deployment where 'main' is always deployable.
17