go-checker

Use before running any go-checker tool to ensure the Go environment is ready. Checks Go version and installs any missing tools. <example> Context: User asks to lint a Go repository. user: "lint my Go code" assistant: "I'll check the Go environment first before running the linter." <commentary> The go-tool-installer agent runs before go-checker skills to validate the environment. </commentary> </example> <example> Context: User invokes vuln-scan explicitly. user: "/go-checker:vuln-scan" assistant: "Let me verify your Go version and tools before running govulncheck." <commentary> govulncheck requires Go 1.21+; the agent warns and skips if version is too old. </commentary> </example>

Use when the user asks about Go dependencies, go.mod, go.sum, or module verification. Trigger on phrases "dependencies", "go mod", "verify deps", "tidy deps", "module check", "dependency audit". Runs go mod verify and/or go mod tidy.

Use when the user wants to generate Go documentation, API docs, or browse package docs. Trigger on phrases "documentation", "API docs", "godoc", "swagger", "openapi", "generate docs". Supports godoc (browser UI) and swag (OpenAPI/Swagger YAML).

Use when the user mentions Go code quality, linting, or static analysis. Trigger on phrases "lint", "code quality", "golangci", "check code style", "static analysis", "run linter". Runs golangci-lint on the Go repository.

Use when the user wants to profile Go CPU performance, run benchmarks, or analyze CPU hotspots. Trigger on phrases "profile", "cpu performance", "pprof cpu", "benchmark", "cpu profiling". Runs go test -bench and opens pprof web UI.

Use when the user wants to profile Go memory usage, heap allocations, or memory leaks. Trigger on phrases "memory profile", "heap", "pprof memory", "memory usage", "allocations", "memory leak". Runs go test -bench with memprofile and opens pprof web UI.