go-dev

Generates and runs statistically useful Go benchmarks with allocation and profile analysis. Use for benchmark creation or measured performance comparison; do not use for general correctness tests.

Detects project build systems and fixes compiler or generated-code failures until every detected build is clean. Use for active build errors; do not use for lint-only cleanup.

Explains targeted Go files, functions, or packages with focused diagrams and idiom analysis. Use when understanding existing Go code; do not use when implementation or refactoring is requested.

Idiomatic Go: interfaces, error handling, concurrency, testing, package layout, and debugging. Use when the user writes, reviews, or debugs Go code, or asks any open Go question that doesn't fit a more specific child skill. SKIP for Go performance/profiling work (use go-profiling-optimization) and explicit Gopher Guides training/API requests (use gopher-guides).

Profile and optimize Go performance: pprof CPU/memory/block/mutex profiles, allocation analysis, escape analysis, sync.Pool, GOGC/GOMEMLIMIT tuning, benchmarks with -benchmem, PGO workflow, execution tracing. Use when user asks 'why is this slow', 'is this allocating', mentions pprof/profiling, runs benchmarks, or needs to reduce p99 latency. SKIP for general Go idioms — use `go` skill.

Finds and fixes Go lint findings while preserving behavior and verifying the result. Use for golangci-lint or formatting failures; do not use for compiler-only failures.

Profiles Go CPU and memory behavior, identifies bottlenecks, and verifies measured optimizations. Use for evidence-driven performance work; do not use for benchmark generation alone.

Finds and safely removes dead Go code, orphaned tests, and avoidable complexity with verification. Use for behavior-preserving cleanup; do not use for product feature changes.

Generates idiomatic table-driven Go tests for a selected file, function, or package and verifies them. Use when test coverage is missing; do not use to diagnose an existing test failure.

Validates fenced bash, sh, shell, and zsh blocks in plugin Markdown with syntax checks, conservative command classification, guarded execution, and portability review. Use after editing command or skill Markdown or when its shell validation fails.

Runs the complete project verification stack and fixes safe failures until blocking checks pass. Use before push or handoff; do not use when only one known test needs diagnosis.