Validates gokit Go module changes with scoped build, test, lint, and vuln-scan tasks via toven.
npx skills add https://github.com/kbukum/gokit --skill validate-kbukum
Please help me install this Agent Skill. Skill: validate Source: https://github.com/kbukum/gokit/tree/main/.github/skills/validate Command: npx skills add https://github.com/kbukum/gokit --skill validate-kbukum
-race -count=1 -shuffle=on flags, target single tests, or watch mode for reruns on change. - Lint compliance: Handles the gofumpt-vs-gofmt gap so golangci-lint passes, plus module selectors, dependency/workspace expansion, caching, and JSONL output for programmatic parsing. - Use Case: After editing the media module, run toven test --module go:media -- -race -count=1 -shuffle=on and toven lint --module go:media to confirm the change is green before handing it to the maintainer. ## Quick Start Ask the assistant to validate your gokit change by running the affected-module tests and lint through toven before committing.High-intent search queries and answers about installing and using this skill.
Use toven's affected-set detection: run `toven affected test --base origin/main --merge-base` to see the blast radius, then `toven test --base origin/main --merge-base` to execute tests only for modules the diff touches, including reverse dependents.
Pass test flags verbatim after `--`, since toven's default test selector excludes `-race`. Run `toven test --module go:<name> -- -race -count=1 -shuffle=on`, which matches gokit's required green baseline.
golangci-lint in this repo enforces gofumpt, which is stricter than gofmt, but `toven format` runs plain `gofmt -w`. Run `gofumpt -w` on the changed directories first, then run `toven lint --module go:<name>`.
Use `toven plan test` to preview what a task would run and where, or `toven explain test --module go:media` to see the exact argv for a single module, without executing anything.
Yes, toven supports JSONL output for programmatic parsing. Run `toven --output jsonl test --base origin/main --merge-base` to get structured results instead of a terminal table.
Full-tree runs are reserved for audits and CI sign-off. Escalate beyond the affected set only when the change is genuinely tree-wide or you are preparing a release; otherwise scope to changed modules.
PeterBookerTidy and verify Go module dependencies with checksum validation.
All-The-VibesCommit changes, push to the remote, and open a pull request for handoff.
mzffreyvazovAnalyze Java project architecture for package boundaries, dependency direction, and layering.
simonnordbergInitialize Go projects with module, linting, and Makefile scaffolding.