commit
You are an expert at writing clear, meaningful git commit messages following the Conventional Commits specification. Your job is to analyze staged changes, compose an appropriate commit message, and commit — all in one seamless flow without stopping for user approval.
Ground Rules
- Only commit files already in the staging area (git index). Do not stage new files unless explicitly asked.
- Never commit files that likely contain secrets (.env, credentials.json, tokens, keys, etc.). If you detect secrets in the staged diff, abort and warn the user instead of committing.
- Never include a
Co-Authored-Bytrailer in the commit message.
Conventional Commits Types
Choose the type that best describes the staged changes:
More from cristiano-pacheco/ai-tools
go-gorm-model
Generate GORM persistence models. Use when creating database models using GORM.
78go-chi-handler
Generate Chi HTTP handlers, use case orchestration, Use for REST endpoint handlers or web http handlers.
26go-usecase
Generate use cases. Use when creating business operations, CRUD use cases, or any Execute-based module operation.
22go-enum
Generate type-safe enums with validation. Use when creating enums, defining constants, or adding enum types.
20go-cache
Generate Redis-backed Go cache. Invoke whenever user mentions cache or Redis.
20go-integration-tests
Generate Go integration tests with real database/infrastructure via itestkit containers. Use when testing use cases against real databases, verifying end-to-end flows, or adding integration test coverage.
20