go-dev-guidelines

Name: go-dev-guidelines
Availability: InStock
Author: Jumppad

Enforce idiomatic Go patterns, TDD workflows, and testing practices.

262|29|Updated Nov 28, 2019

Search Tags:#code quality #testing #tdd #development #best practices #golang #go

Ready to run

npx skills add https://github.com/jumppad-labs/jumppad --skill go-dev-guidelines

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: go-dev-guidelines
Source: https://github.com/jumppad-labs/jumppad/tree/main/.claude/skills/go-dev-guidelines
Command: npx skills add https://github.com/jumppad-labs/jumppad --skill go-dev-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps Go developers write high-quality, maintainable, and testable code by providing clear, idiomatic guidelines. It reduces common pitfalls and inconsistencies, streamlining the development process and ensuring adherence to best practices.

Core Features & Use Cases

Idiomatic Go Patterns: Guides on project structure, naming conventions, error handling, and concurrency.
TDD Workflow: Enforces a Test-Driven Development approach using testify/require for assertions and mockery for mocks.
Use Case: When starting a new Go microservice, activate this skill to ensure the project adheres to a consistent, testable, and maintainable architecture from day one, saving future refactoring time.

Quick Start

When writing a new Go feature, ask me to apply the 'go-dev-guidelines' skill to ensure TDD, proper error handling, and idiomatic Go patterns are followed.

Frequently Asked Questions about go-dev-guidelines

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

FAQPage Schema

How do I structure a new Go project to follow best practices?▼

Go projects should follow idiomatic patterns with standardized directory layouts, small focused interfaces, constructor-based dependency injection, and explicit error handling. This Skill provides the architectural guidelines to set up maintainable, testable Go services from the start, avoiding refactoring later.

What's the best way to implement Test-Driven Development in Go?▼

TDD in Go uses testify/require for assertions and mockery for mock generation stored in mocks/. This Skill enforces a complete TDD workflow that ensures comprehensive test coverage before implementation, reducing bugs and improving code quality.

How do I ensure my Go code follows idiomatic patterns and passes quality checks?▼

Idiomatic Go enforces go vet, gofmt formatting, and godoc documentation standards. This Skill applies these tools and patterns consistently across services and packages, eliminating coding inconsistencies and maintaining readability.

When should I apply Go development guidelines to my project?▼

Apply these guidelines when creating new features, refactoring existing code, or writing tests across Go services. Starting with them from day one standardizes practices and prevents accumulation of technical debt in microservices.

Can I use this approach with existing Go projects or only new ones?▼

These guidelines apply to both new Go microservices and existing codebases undergoing refactoring or new feature development. They enforce consistent patterns incrementally without requiring a complete rewrite.

What testing tools does Go development guidelines require?▼

This Skill requires mockery for mock generation and testify/require for test assertions. These tools are standard Go testing dependencies that enable automated mocking and clear, maintainable test code.