golang-cli-review
Comprehensive code review for Golang CLI applications. Produces an actionable checklist covering error handling, CLI framework patterns (Cobra/urfave), testing, performance, security, and Go idioms. TRIGGERS: Review Go CLI, review golang command-line, code review .go CLI, audit CLI application, check golang tool, review cobra app
Best use case
golang-cli-review is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Comprehensive code review for Golang CLI applications. Produces an actionable checklist covering error handling, CLI framework patterns (Cobra/urfave), testing, performance, security, and Go idioms. TRIGGERS: Review Go CLI, review golang command-line, code review .go CLI, audit CLI application, check golang tool, review cobra app
Teams using golang-cli-review should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/golang-cli-review/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How golang-cli-review Compares
| Feature / Agent | golang-cli-review | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Comprehensive code review for Golang CLI applications. Produces an actionable checklist covering error handling, CLI framework patterns (Cobra/urfave), testing, performance, security, and Go idioms. TRIGGERS: Review Go CLI, review golang command-line, code review .go CLI, audit CLI application, check golang tool, review cobra app
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Go CLI Code Review Review Go CLI applications and produce an actionable checklist of findings. ## Review Workflow 1. **Gather code** - Read all Go files in the CLI project 2. **Analyze** - Evaluate against review categories (see below) 3. **Produce checklist** - Use template from [references/review-checklist.md](references/review-checklist.md) ## Review Categories Evaluate each area systematically: ### CLI Structure & Framework - Framework usage (prefer Cobra for complex CLIs) - Command hierarchy and discoverability - Help text quality with examples - Version command following semver ### Error Handling - RunE vs Run (must return errors) - Error wrapping with `%w` and context - User-facing error actionability - Meaningful exit codes (0=success, 1=error, 2=usage) - No panics in normal paths ### Flag & Argument Design - Lowercase-kebab-case naming - Short flags for common options (`-v`, `-o`, `-q`) - Required flags marked and validated early - Sensible defaults - Clear descriptions ### Input/Output - stderr for errors/progress, stdout for data - Machine-readable output support (`--json`, `--format`) - Quiet and verbose mode support - Non-TTY mode handling (no prompts) ### Security - Secrets via env vars or files, never flags - Path traversal prevention - No shell injection - URL scheme validation - No sensitive data in logs ### Testing - Command-level unit tests - Error path coverage - Integration tests for critical flows ### Performance & Resources - Context-based cancellation - Signal handling (SIGINT/SIGTERM) - Proper resource cleanup (defer) - No goroutine leaks ### Go Idioms - Effective Go style compliance - Immediate error handling - Package naming conventions - Interface/struct patterns ## Reference Material For patterns and examples, see [references/cli-patterns.md](references/cli-patterns.md). ## Output Format Use the checklist template from [references/review-checklist.md](references/review-checklist.md): ``` ## Critical Issues - [ ] **[C1]** `file.go:123` - Description - **Impact:** ... - **Fix:** ... ## Warnings - [ ] **[W1]** `file.go:45` - Description - **Why:** ... - **Fix:** ... ## Suggestions - [ ] **[S1]** `file.go:78` - Description - **Consider:** ... ## Positive Patterns - **[P1]** `file.go:90` - What was done well ``` Severity levels: - **Critical**: Security issues, crashes, data loss - must fix - **Warning**: Bugs, anti-patterns, maintenance concerns - should fix - **Suggestion**: Style, optimization, minor improvements - nice to have - **Positive**: Good practices worth highlighting
Related Skills
superbuild
Use when executing implementation plans phase-by-phase with strict enforcement of quality gates, tests, and Definition of Done. Triggers on "build this plan", "execute plan", "implement phases", or when user provides a plan document to execute.
teach
Transforms technical documents into rigorous learning journeys with collegiate-level mastery requirements. Uses Bloom's taxonomy progression, 80%+ mastery thresholds, and multi-level verification before advancing. Treats learning as a high school to college graduation progression. Use when user wants deep understanding, not surface familiarity.
superplan
Use when starting significant features, epics, or complex tasks. Creates multi-phase implementation plans with parallelizable phases, poker estimates, TDD-first acceptance criteria, and quality gates. Detects tech stack from CLAUDE.md/AGENTS.md (bypassing internet research if complete) or via codebase scan.
skulto-release-cert
Certify a skulto build for Homebrew prod release. Runs three passes — unit/lint/cross-compile, clean-slate CLI walkthrough, and security audit — then produces a certification summary.
autobuild
Autonomous single-shot plan execution. Runs entire superplan implementation plans without stopping, using sub-agents for each phase. Phases write state to filesystem for resume capability. Sequential phases run in order, parallel phases (1a, 1b) run concurrently. User never needs to compact context.
flutter-dart-code-review
库无关的Flutter/Dart代码审查清单,涵盖Widget最佳实践、状态管理模式(BLoC、Riverpod、Provider、GetX、MobX、Signals)、Dart惯用法、性能、可访问性、安全性和整洁架构。
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
golang-patterns
Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.
security-review
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
addressing-pr-review-comments
Address all valid review comments on a PR for the current branch in the streamlit/streamlit repo. Covers both inline review comments and general PR (issue) comments. Use when a PR has reviewer feedback to address, including code changes, style fixes, and documentation updates.
lightning-architecture-review
Review Bitcoin Lightning Network protocol designs, compare channel factory approaches, and analyze Layer 2 scaling tradeoffs. Covers trust models, on-chain footprint, consensus requirements, HTLC/PTLC compatibility, liveness, and watchtower support.
grpc-golang
Build production-ready gRPC services in Go with mTLS, streaming, and observability. Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport.