agents-go

Enforce Go backend project structure and coding rules.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/yanun0323/.codex --skill agents-go
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agents-go
Source: https://github.com/yanun0323/.codex/tree/main/skills/agents-go
Command: npx skills add https://github.com/yanun0323/.codex --skill agents-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes and enforces Go backend project identity, architecture, and coding conventions to prevent drift and inefficiency.

Core Features & Use Cases

  • Enforces a consistent project structure, entry points, and folder ownership across Go services.
  • Guides error handling, concurrency, initialization, API contracts, testing, and infra triggers to improve reliability and onboarding.
  • Use Case: When starting or reviewing a Go backend project, apply these rules to verify alignment with the repository's architecture and conventions.

Quick Start

Apply these rules to a Go backend repository to ensure architecture, layering, and best practices compliance.

Frequently Asked Questions about agents-go

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

FAQPage Schema
How do I enforce Go backend project structure and coding rules to prevent architectural drift?

You prevent architectural drift in Go backend services by enforcing hard constraints on folder ownership, import boundaries, and initialization, ensuring safe, testable, and maintainable code across monolithic services with a single main binary.

What is the best way to guide concurrency lifecycle and error handling in a Go monolithic service?

To guide concurrency lifecycle and error handling in a Go monolithic service, apply defined entry points and hard constraints that specify safe initialization, concurrency boundaries, and reliable error handling rules.

Does this backend governance approach work for monolithic Go services with a single main binary?

Yes, this backend governance approach works specifically for monolithic Go services with a single main binary and defined entry points, applying rules to verify alignment with repository architecture and coding conventions.

How do I verify API contracts and testing compliance when reviewing a Go backend project?

To verify API contracts and testing compliance in a Go backend project, apply governance rules that guide identity, layering, initialization, and infra triggers to ensure alignment with the repository's architecture and conventions.

When should I not use strict architectural governance rules for my Go backend?

You should not use strict architectural governance rules for Go backends that are not monolithic services with a single main binary, as the hard constraints on folder ownership and import boundaries are designed for defined entry points.