go

Orchestrate a Go delivery workflow from requirements through validation and review.

2|Updated Aug 4, 2025
One-click install
npx skills add https://github.com/zhu327/go-clean-arch --skill go-zhu327
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go
Source: https://github.com/zhu327/go-clean-arch/tree/main/.cursor/skills/go
Command: npx skills add https://github.com/zhu327/go-clean-arch --skill go-zhu327

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you carry a Go change from requirements to implementation, validation, review, and simplification in a controlled, end-to-end workflow.

Core Features & Use Cases

  • Requirements-first delivery: Starts with design and approval before implementation so scope stays aligned.
  • Repository-aware execution: Adapts to the project’s own commands, architecture, and validation steps instead of assuming a fixed toolchain.
  • Quality gates: Includes planning, test-driven development, validation, code review, and simplification to reduce defects and keep changes maintainable.
  • Use case: Use it for a multi-step Go feature, bug fix, or refactor that needs disciplined delivery across several stages.

Quick Start

Use the go skill to guide this repository change from approved requirements through implementation and validation.

Frequently Asked Questions about go

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

FAQPage Schema
How do I manage a Go feature delivery workflow from requirements to validation?

A Go delivery workflow guides a feature from approved requirements through planning, test-driven development, and validation. It orchestrates staged execution to ensure architecture-aware adaptation and end-to-end quality gates are satisfied before deployment.

What is the best way to enforce test-driven development and code review in a Go project?

Enforcing test-driven development and code review in a Go project requires a disciplined delivery workflow. By integrating validation gates and refactoring stages, the workflow reduces defects and ensures maintainable code cleanup before changes are finalized.

How does repository-aware execution adapt to my existing Go project commands?

Repository-aware execution adapts to your Go project by discovering commands from project documentation. Instead of assuming a fixed toolchain, it aligns staged execution with your repository's specific architecture and validation steps.

Can I use this delivery workflow for a multi-step Go refactor?

Yes, you can use this workflow for a multi-step Go refactor. It applies staged execution to carry repository changes through implementation, validation, code review, and simplification, ensuring the refactoring process maintains disciplined delivery.

When do I need a staged execution workflow for Go code changes?

You need a staged execution workflow for Go code changes when a feature requires architecture-aware adaptation and disciplined delivery. Starting with design and approval before implementation keeps scope aligned and satisfies end-to-end quality gates.