go-development
Go Development Workflow
Workflow for Go code changes in this repository.
Prerequisites
- Use
git-workflowSkill for branch management, commit conventions, and PR creation. - Refer to
.claude/rules/go.mdfor detailed verification commands and coding rules (SSOT).
Applicable Directories
| Directory | Description |
|---|---|
internal/ |
Core application code (Clean Architecture) |
pkg/ |
Reusable shared packages |
cmd/ |
Application entry points |
Workflow
1. Make Changes
Edit Go files following the rules in .claude/rules/go.md.
2. Verify (from rules/go.md)
make go-lint && make tidy && make check-build && make go-test
3. Self-Review Checklist
- Domain layer has ZERO infrastructure dependencies
- Error handling uses
fmt.Errorf("context: %w", err) - No private keys or sensitive data logged
- Auto-generated files not edited
Database Changes
If modifying database schema, use db-migration skill.
Related
.claude/rules/go.md- Go rules (SSOT)git-workflow- Branch, commit, PR workflowdb-migration- Database schema workflow
More from hiromaily/go-crypto-wallet
makefile-update
Makefile development workflow. Use when modifying Makefile or files in make/ directory.
33docs-update
Documentation update workflow. Use when modifying files in docs/ directory or any markdown files (*.md).
33btc-terminology
Critical Bitcoin terminology rules to prevent confusion between bech32m (encoding) and taproot (address type). Use when working on BTC-related code, config files, or shell scripts.
33shell-scripts
Shell script development workflow. Use when modifying files in scripts/ directory or any *.sh files.
33db-migration
Database schema and migration workflow. Use when modifying database schemas in tools/atlas/ or SQLC queries in tools/sqlc/.
30openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
24