go-cli-tui-author

Standardize Go CLI command architecture with go-cliutil enforced patterns.

1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/mikeschinkel/ai-agent-depot --skill go-cli-tui-author
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-cli-tui-author
Source: https://github.com/mikeschinkel/ai-agent-depot/tree/main/skills/go-cli-tui-author
Command: npx skills add https://github.com/mikeschinkel/ai-agent-depot --skill go-cli-tui-author

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Author and refactor Go CLI commands using go-cliutil's enforced architecture and Mike's Go house rules (ClearPath, doterr, go-dt). Use whenever creating/modifying commands.

Core Features & Use Cases

  • Enforces a main entrypoint pattern and a dedicated commands package.
  • Provides a ready-to-use skeleton for new commands consistent with go-cliutil.
  • Helps maintain readability and testability across CLI tools in Go projects.

Quick Start

Create a new command following the provided skeleton and integrate it with RunCLI in the repo.

Frequently Asked Questions about go-cli-tui-author

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

FAQPage Schema
How do I structure a Go CLI project to maintain consistent command architecture?

Structure a Go CLI project by enforcing a single main entrypoint, a dedicated commands package, and one command per file. This pattern standardizes command development and maintains readability across CLI tools.

What is the best way to organize multiple commands in a Go CLI application?

Organize multiple commands by placing each in its own file within a dedicated commands package. This structured registration approach ensures command hierarchies remain testable and maintainable.

Does this approach require specific Go libraries for error handling and execution paths?

Yes, the approach requires using the doterr library for error handling and clearpath for execution paths. These libraries enforce architectural rules and ensure consistent CLI behavior.

Can I use this command skeleton to refactor an existing Go CLI tool?

Yes, you can refactor existing Go CLI tools by migrating commands into the provided skeleton. This enforces a standardized structure using go-cliutil, ensuring your application meets architectural requirements.

Why should I use a single entrypoint pattern for my Go CLI commands?

Use a single entrypoint pattern to centralize command registration and execution via RunCLI. This prevents fragmented initialization and ensures all commands adhere to the same architectural rules.