go-dev

Guide Go code implementation, testing, debugging, and review across modules and CI pipelines.

Updated Jul 10, 2023

Search Tags:#testing #linting #debugging #go #code-review #go-modules

Ready to run

npx skills add https://github.com/iamtatsuki05/dotfiles --skill go-dev-iamtatsuki05

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: go-dev
Source: https://github.com/iamtatsuki05/dotfiles/tree/main/dotfiles/.agent/skills/go-dev
Command: npx skills add https://github.com/iamtatsuki05/dotfiles --skill go-dev-iamtatsuki05

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill guides developers through implementing, refactoring, testing, debugging, and reviewing Go code, reducing cycle time and improving code quality.

Core Features & Use Cases

Code implementation guidance: quickly scaffold new features or modules with best practices.
Quality assurance support: design tests, reviews, and error handling patterns to catch regressions early.
Real-world scenarios: for Go modules, concurrency, interfaces, generics, and vetting test/build pipelines across projects.

Quick Start

Review the provided Go module and propose concrete changes to pass tests and align with project standards.

Frequently Asked Questions about go-dev

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

FAQPage Schema

How do I implement and test Go modules with proper error handling?▼

To implement and test Go modules, you scaffold features using safe patterns, design tests to catch regressions early, and enforce proper error handling alongside standard tooling requirements like go.mod and golangci-lint.

What is the best way to review Go code for concurrency and generics?▼

Reviewing Go code for concurrency and generics requires applying safe patterns and proper error handling across small to large codebases, ensuring standard tooling requirements are met through vetting test and build pipelines.

Do I need a Makefile and golangci-lint to debug Go code?▼

Yes, debugging Go code effectively requires standard tooling like a Makefile, golangci-lint, and go vet to enforce safe patterns, apply proper error handling checks, and validate code quality across your modules.

Can I use this approach to refactor Go interfaces in large codebases?▼

Yes, you can refactor Go interfaces in large codebases by applying safe patterns and proper error handling, using standard tooling requirements to guide implementation and review across the project.

Why does my Go build pipeline fail standard vetting checks?▼

Your Go build pipeline fails standard vetting checks when code lacks safe patterns or proper error handling, requiring alignment with standard tooling requirements like go.mod, Makefile, golangci-lint, and vet to pass.