Go
Skill chinayin/gox-claude-plugins/plugins/gox-code-rules/skills/go
Team coding-standards plugins for Claude Code (Agent Skills marketplace) · 面向 Claude Code 的团队代码规范插件(技能 marketplace)
npx -y skills add chinayin/gox-claude-plugins --skill goAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Team Go microservice architecture and coding standards. Use this whenever designing or writing Go code in this repo — CLI commands (cobra), configuration (gox/config), database migrations (goose), or project scaffolding (Makefile/CI). Consult it any time you touch Go code or plan a Go module — including small changes like reading a single environment variable, secret, or config value — even if the user never says "standards".
SKILL.md
2.1 KB, 406 tokens by cl100k_base, as published. Nobody here has run it
Team Go Standards
Follow team conventions when writing or designing Go code in this repo. Reply and write code comments in Chinese. Read the detailed standards in references/ on demand per the index below — do not read them all at once, only the file relevant to the current task.
When to read which (index)
| What you're doing | Read this |
|---|---|
| Writing any Go code (baseline: versions, logging, errors, concurrency, naming…) | references/rules.md ← read first by default |
Designing/writing CLI commands under cmd/** (cobra + gox/cli) | references/cli.md |
Configuration loading (config/**, main.go/config.go, bootstrap/, gox/config) | references/config.md |
Database migrations / schema (migrations/, dbmigrate/, store.go, *migrate*, *migration*, *schema*, goose) | references/db-migrations.md |
Project scaffolding (Makefile, .gitignore, .editorconfig, .golangci-lint-version, .github/workflows/*.yml) | references/scaffold.md |
Core rules (highest priority; details in rules.md)
- Go 1.26+; JSON/protobuf fields use snake_case.
- Logging: initialize gox/log at the entry point, use log/slog in business code; never log with fmt.
- Config: use gox/config exclusively; never use viper directly or bare
os.Getenvin business code. - All external calls must set a timeout (internal 10s, external 30s).
- No package-level mutable global state; wrap errors with a package prefix.
These are in-session soft guidance; the final enforcement is the repo's
golangci-lint/ CI / PR review.
Gives 0 of the 12 instructions most project setup skills give in 406 tokens
Counted across 999 of the 1,637 authors here whose files we hold, read 2026-08-06
- ask one question at a timein 29 of 999, across 28 files
- detect the package manager from lockfilesin 28 of 999, across 9 files
- present findings to the userin 25 of 999, across 4 files
- explore current repo statein 24 of 999, across 3 files
- update the agent skills block in place if it existsin 24 of 999, across 3 files
- install husky lint-staged and prettierin 23 of 999, across 4 files
- create the lintstagedrc filein 22 of 999, across 3 files
- commit all changed filesin 22 of 999, across 3 files
- run lint-staged to verify it worksin 22 of 999, across 3 files
- initialize huskyin 21 of 999, across 2 files
- create the husky pre-commit filein 21 of 999, across 2 files
- create a prettierrc file if missingin 21 of 999, across 2 files
Said here and by no other author read
- reply and write code comments in chinese
- read detailed standards in references on demand
- read rules.md first by default
- use go 1.26 or higher
- use snake_case for json and protobuf fields
- initialize gox/log at the entry point
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.