git-commit
Structured git commit messages following Conventional Commits format for Go projects. Generates well-scoped, atomic commits with clear descriptions. Use when committing changes, writing commit messages, preparing PRs, or reviewing commit history quality. Trigger examples: "commit these changes", "create commit", "commit message", "prepare PR", "squash commits". Not for: code review (go-code-review), changelog generation.
- License 许可
- MIT
- 最近更新
- 2026-10-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- git-commit
- license
- MIT
- metadata
- { "author": "eduardo-sl", "version": "1.2.1" }
- description
- Structured git commit messages following Conventional Commits format for Go projects. Generates well-scoped, atomic commits with clear descriptions. Use when committing changes, writing commit messages, preparing PRs, or reviewing commit history quality. Trigger examples: "commit these changes", "create commit", "commit message", "prepare PR", "squash commits". Not for: code review (go-code-review), changelog generation.
- allowed-tools
- Read Glob Grep Bash(git:*)
- compatibility
- Designed for Claude Code or similar AI coding agents. Requires git.
- user-invocable
- true
03 SKILL.md 正文
Git Commit Standards
Commits tell the story of your codebase. A good commit history is worth more than any amount of documentation — because it's always up to date.
1. Conventional Commits Format
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
Types:
| Type | When |
|---|---|
feat |
New feature (correlates with MINOR in semver) |
fix |
Bug fix (correlates with PATCH in semver) |
refactor |
Code change that neither fixes a bug nor adds a feature |
perf |
Performance improvement |
test |
Adding or correcting tests |
docs |
Documentation changes only |
chore |
Build process, tooling, dependencies |
ci |
CI/CD configuration changes |
style |
Formatting, whitespace (not CSS — code formatting) |
Scope:
Use the package name or module area:
feat(auth): add JWT refresh token rotation
fix(store/postgres): handle connection pool exhaustion
refactor(service): extract validation into dedicated package
test(handler): add table-driven tests for user endpoints
chore(deps): bump go.uber.org/zap to v1.27.0
Breaking changes:
feat(api)!: change pagination from offset to cursor-based
BREAKING CHANGE: The `offset` and `limit` query parameters are replaced
by `cursor` and `page_size`. All existing clients must migrate.
2. Commit Message Rules
Subject line:
- Imperative mood: "add feature", NOT "added feature" or "adds feature"
- Lowercase after type prefix
- No period at the end
- Max 72 characters
- Must describe WHAT changed, not HOW
Body (when needed):
- Blank line between subject and body
- Explain WHY the change was necessary
- Explain WHAT is different at a high level
- Wrap at 72 characters
Footer:
- Reference issues:
Fixes #123,Closes #456,Refs #789 - Co-authors:
Co-authored-by: Name <email> - Breaking changes:
BREAKING CHANGE: description
3. Examples
Simple change:
fix(handler): return 404 instead of 500 for missing user
With body:
refactor(service): replace manual SQL with sqlx named queries
The raw SQL string concatenation for dynamic WHERE clauses was
error-prone and difficult to maintain. sqlx named queries provide
the same flexibility with automatic parameter binding.
No behavior change — all existing tests pass.
Breaking change:
feat(config)!: migrate from YAML to environment variables
BREAKING CHANGE: Configuration is now loaded from environment
variables instead of config.yaml. See README.md for the full
list of supported variables.
Closes #234
Dependency update:
chore(deps): upgrade pgx to v5.5.0
Picks up connection pool improvements and fixes for
COPY protocol handling. See release notes:
https://github.com/jackc/pgx/releases/tag/v5.5.0
4. Atomic Commits
Each commit should be ONE logical change that:
- Compiles on its own (
go build ./...passes) - Tests pass (
go test ./...passes) - Can be reverted independently without breaking other changes
Split large changes:
# ❌ Bad — one commit doing everything
feat(user): add user management with CRUD, validation, auth, and tests
# ✅ Good — atomic, reviewable commits
feat(domain): add User entity and validation rules
feat(store): implement PostgreSQL user repository
feat(service): add user service with create and get operations
feat(handler): add REST endpoints for user management
test(service): add table-driven tests for user creation
docs(api): document user endpoints in OpenAPI spec
5. Pre-Commit Verification
Before committing, run:
# Format and lint
goimports -w .
golangci-lint run
# Build
go build ./...
# Test
go test -race ./...
# Tidy modules
go mod tidy
If any step fails, fix before committing. Never commit broken code with "will fix later" — you won't.
6. Commit Workflow
# Stage specific files (not git add .)
git add internal/service/user.go
git add internal/service/user_test.go
# Review staged changes
git diff --staged
# Commit with message
git commit -m "feat(service): add user creation with email validation"
# Or use editor for longer messages
git commit # opens $EDITOR
Interactive rebase before PR:
Interactive rebase opens $EDITOR, so an agent cannot drive it. Prepare
fixups non-interactively, then hand the final step to the developer:
# Mark a commit as a fixup of an earlier one (no editor)
git commit --fixup <sha>
# Collapse them automatically (no editor with --autosquash + GIT_SEQUENCE_EDITOR)
GIT_SEQUENCE_EDITOR=: git rebase -i --autosquash main
For reordering or rewording, tell the developer to run git rebase -i main
themselves rather than attempting it.
7. What NOT to Commit
- Generated files (
*.pb.gounless required,mocks/) - IDE configuration (
.idea/,.vscode/— use global gitignore) - OS files (
.DS_Store,Thumbs.db) - Binaries and build artifacts
.envfiles with secretsvendor/(unless explicitly required by project policy)
04 同仓库更多 Skills
tb-writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
tb-using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
tb-test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
tb-subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
tb-scrutinize
Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler/more elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on /tb-scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.
tb-requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements