golang-cli-review

This skill acts as a specialized quality assurance agent for Golang command-line interface development. It is designed to assist software engineers in maintaining high-quality codebases by providing a systematic audit against established Go ecosystem standards. Whether you are building complex tools with Cobra, urfave/cli, or standard library flags, this agent performs a deep dive into your project structure to identify potential bottlenecks, security vulnerabilities, and departures from Go best practices.

The agent analyzes your codebase to ensure that error handling, input/output operations, and concurrency patterns follow idiomatic Go conventions. It helps transition developers from basic scripts to production-grade tools by identifying missing test coverage, inefficient flag designs, and improper resource management. It is particularly valuable during pull request reviews or as part of a continuous integration pipeline for CLI-focused repositories.

• Performs comprehensive framework-specific audits for Cobra and urfave/cli patterns, including command hierarchy, help text quality, and versioning.

• Evaluates critical error handling practices, verifying proper error wrapping (%w), context usage, and correct application exit codes (0, 1, 2).

• Audits security and safety by checking for secret leakage via flags, shell injection risks, and path traversal vulnerabilities.

• Analyzes performance and resource cleanup, ensuring proper use of context for cancellation and prevention of goroutine leaks.

• Inspects Go idiom compliance, checking for effective Go style, interface/struct patterns, and package naming conventions.

• Produces an actionable, severity-ranked checklist (Critical, Warning, Suggestion, Positive) to guide refactoring and remediation efforts.

• Best used on projects structured with standard Go CLI patterns where automated, consistent feedback is required.

• Requires read access to the target repository files to perform analysis.

• The output is provided as a structured checklist; users should review each point to determine if a fix is necessary based on project-specific constraints.

• Focuses on command-level unit tests and integration flow robustness.

• Output format is optimized for machine readability and direct integration into developer workflows.