conventional-commits
Conventional Commits
Structured commit message format for version control that provides clear, readable project history.
Overview
The Conventional Commits specification provides:
- Automated changelog generation - Tools can parse commits to generate CHANGELOG.md
- Semantic versioning - Commit types map to version bumps (feat → minor, breaking → major)
- Clear project history - Standardized format makes git log readable
- Automated releases - CI/CD can trigger releases based on commit types
Quick Reference
More from tigrisdata/skills
tigris-object-operations
Use when working with objects in Tigris Storage - uploading, downloading, deleting, listing, getting metadata, or generating presigned URLs
70tigris-bucket-management
Use when creating, listing, inspecting, or deleting Tigris Storage buckets
67go-table-driven-tests
Write Go table-driven tests following established patterns. Use when writing tests, creating test functions, adding test cases, or when the user mentions "test", "table-driven", "Go tests", or testing in Go codebases.
67tigris-snapshots-forking
Use when needing point-in-time recovery, version control for object storage, or creating isolated bucket copies for testing/experimentation
64file-storage
Use when working with Tigris file storage - uploading, downloading, deleting, listing files, presigned URLs, client uploads, or setting up Tigris CLI and SDK. Covers Next.js, Remix, Express, Rails, and Laravel. For Python/Django, see the tigris-python-sdk skill.
42installing-tigris-storage
Use when setting up @tigrisdata/storage in a new project or configuring authentication and bucket access
37