skills.rest
pszypowicz
pszypowiczCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

go-dev

Verify Go APIs with go doc before coding and run gofmt, go vet, go build, and go test -race.

Updated Apr 7, 2026
Search Tags:#testing#verification#go#code-quality#static-analysis#toolchain#go-fix
One-click install
npx skills add https://github.com/pszypowicz/claude-skills --skill go-dev-pszypowicz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: go-dev
Source: https://github.com/pszypowicz/claude-skills/tree/main/plugins/go-dev/skills/go-dev
Command: npx skills add https://github.com/pszypowicz/claude-skills --skill go-dev-pszypowicz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Go development often suffers from brittle workflows where verification and quality checks lag behind code changes. This skill enforces a toolchain-first verification workflow to validate APIs, compile, test, and modernize Go code early in the process.

Core Features & Use Cases

  • Toolchain-first verification: verify signatures with go doc, build, test, and static analysis before coding or merging.
  • Modernization guidance: apply go fix and use features between Go 1.21-1.26 to keep code up to date.
  • Use Case: When refactoring a Go module, run the integrated verification workflow to catch issues before changes reach CI.

Quick Start

Start a Go session with the toolchain-first workflow to verify APIs before writing code and run the standard checks after changes.

Frequently Asked Questions about go-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Go API signatures before writing code?▼

Post-change quality checks in Go involve running gofmt, go vet, go build, and go test -race. This workflow enforces these static analysis and testing tools to catch issues before changes reach CI.

How do I modernize Go modules across versions 1.21 to 1.26?▼

Modernizing Go modules uses go fix and version-aware features for Go 1.21 through 1.26. This toolchain workflow applies modernization guidance to keep code up to date with workspace and module tips.

What is the best way to integrate static analysis into Go refactoring?▼

Integrating static analysis into Go refactoring involves a toolchain-first verification workflow. Running integrated go vet and build checks early catches issues before code changes reach CI, preventing brittle lagging workflows.

Does this Go development workflow require specific dependencies?▼

This Go development workflow requires no external dependencies. It relies on standard toolchain commands including go doc, gofmt, go vet, go build, go test -race, and go fix for verification and modernization.

When do I need a toolchain-first verification workflow for Go?▼

A toolchain-first verification workflow is needed when writing, editing, debugging, testing, or modernizing Go code. It prevents brittle development by enforcing API validation and quality checks early in the process.

Related Skills

Explore More Software Engineering Skills→
ronniegeraghtyronniegeraghty
3

testing-patterns

Validate Go testing patterns with table-driven tests, race detection, and stubs.

Community
Advanced
YukiIto1999YukiIto1999

analyzing-golang-malware-with-ghidra

Recover function names and Go runtime metadata from stripped Go malware binaries with Ghidra.

Community
Advanced
linskybinglinskybing

code-validation-standards

Automate Go code validation across pre-commit and pre-push hooks.

Community
Intermediate
tamago0224tamago0224

golang-security

Identify security vulnerabilities in Go code using govulncheck and static analysis.

Community
Advanced