go

Enforces Go coding standards for vertical slicing, result patterns, and domain rule routing.

1|Updated Jul 18, 2025
One-click install
npx skills add https://github.com/AdelysAlberto/md-configs-and-agents --skill go-adelysalberto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: go
Source: https://github.com/AdelysAlberto/md-configs-and-agents/tree/main/agents-hermes/skills/go
Command: npx skills add https://github.com/AdelysAlberto/md-configs-and-agents --skill go-adelysalberto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Go projects often drift into inconsistent architectures, scattered error handling, and unverified code changes. This Skill provides a set of non-negotiable Go coding directives that keep codebases modular, explicit, and verified before every commit. ## Core Features & Use Cases - Vertical Slicing Enforcement: Groups all business domain code by module inside src/modules/<FeatureName>/ for clear feature boundaries. - Result Pattern Mandate: Requires services to return explicit result objects ({ success, value/error }) instead of throwing exceptions. - Domain Rule Routing: Routes HTTP, testing, database, concurrency, and configuration work to dedicated rule files such as rules/go-http.rules.md and rules/go-testing.rules.md. - Use Case: When an AI agent edits any **/*.go file, it automatically applies these directives, runs the linter before committing, and prefers simplification over added complexity. ## Quick Start Apply the Go coding rules to review and refactor the Go files in my project according to the vertical slicing and result pattern directives.

Frequently Asked Questions about go

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

FAQPage Schema
How do I structure a Go project with vertical slicing?▼

Vertical slicing groups all business domain code by feature module inside src/modules/<FeatureName>/ instead of splitting by technical layer. Each module owns its handlers, services, and data access for that feature.

What is the result pattern for error handling in Go services?▼

The result pattern requires services to return explicit result objects shaped as { success, value/error } rather than throwing or propagating exceptions. This makes failure paths explicit and easier for callers to handle.

When does this Go skill activate?▼

It activates as a runtime decision whenever work involves files matching the glob pattern **/*.go. It then routes domain-specific work to rule files for HTTP, testing, database, concurrency, and configuration topics.

What checks should run before committing Go code?▼

The directives require running the linter before every commit as a pre-commit verification step. Fixes should also simplify the system by removing or consolidating code rather than adding new layers or special cases.

When should I avoid adding new abstractions in Go fixes?▼

Avoid new layers, flags, or special cases when a fix grows the system's surface area. The simplification-first directive prefers removing or consolidating code, so look for the version of the fix that shrinks the system.