Go ci
My personal pi harness configuration.
npx -y skills add nyquistwilder/personal-pi --skill go-ciAssembled 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
Go CI workflow for reproducible toolchains, module cache, fmt/vet/staticcheck/test/race/build/govulncheck jobs, artifacts, and release gates aligned with local just check.
SKILL.md
1.9 KB, as published. Nobody here has run it
Go CI
Rule
CI must mirror local validation and make failures actionable. Keep just check as the local
source of truth when present.
Hard Stops
Ask before:
- Adding or changing CI providers, paid services, credentials, release secrets, or publishing jobs.
- Requiring nightly/development Go versions or changing the repository toolchain policy.
- Uploading coverage, SBOMs, binaries, or containers to external systems.
- Making CI-only checks that developers cannot run locally.
Defaults
- Use stable Go from project policy with
actions/setup-goon GitHub Actions when GitHub CI is already used or requested. - Cache modules/build cache through official CI mechanisms.
- Run
go mod downloadorgo mod verify,gofmtcheck,go vet,staticcheck,go test ./...,go test -race ./...when affordable,go build ./..., andgovulncheck ./.... - Prefer invoking
just check; keep detailed commands injustfileto align local and CI. - Upload test/coverage artifacts only when the project consumes them.
Workflow
- Inspect local wrappers, Go version policy, existing CI, and release gates.
- Add or update CI to call local wrappers and install required tools reproducibly.
- Configure module/build caches without caching generated artifacts in git.
- Separate fast PR checks from slower scheduled/security/race matrices when needed.
- Validate YAML and run local
just check.
Antipatterns
- CI commands drifting from local
just check. - Installing latest tools with no version policy.
- Ignoring
go.sumchanges or skippinggo mod tidychecks. - Race/security scans only after release.
Completion
Report CI files changed, jobs/checks, toolchain/cache strategy, local validation, and release gates.