How do I install the Adamos486 Skills Golang CLI Review skill?

Run npx skillmds@latest add tomevault-io/adamos486-skills-golang-cli-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Adamos486 Skills Golang CLI Review skill do?

Go CLI Code Review It is listed under Coding & Dev Tools on SkillMD.

Is Adamos486 Skills Golang CLI Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Adamos486 Skills Golang CLI Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Adamos486 Skills Golang CLI Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Adamos486 Skills Golang CLI Review?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Adamos486 Skills Golang CLI Review by tomevault-io

Name: Adamos486 Skills Golang CLI Review
Author: tomevault-io

File contents

Go CLI Code Review

Review Go CLI applications and produce an actionable checklist of findings.

Review Workflow

Gather code - Read all Go files in the CLI project
Analyze - Evaluate against review categories (see below)
Produce checklist - Use template from 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.

Output Format

Use the checklist template from 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

Source: adamos486/skills — distributed by TomeVault.

---name: adamos486-skills-golang-cli-reviewdescription: Go CLI Code Review---# Go CLI Code ReviewReview Go CLI applications and produce an actionable checklist of findings.## Review Workflow1. **Gather code** - Read all Go files in the CLI project2. **Analyze** - Evaluate against review categories (see below)3. **Produce checklist** - Use template from [references/review-checklist.md](references/review-checklist.md)## Review CategoriesEvaluate 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 MaterialFor patterns and examples, see [references/cli-patterns.md](references/cli-patterns.md).## Output FormatUse 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---> Source: [adamos486/skills](https://github.com/adamos486/skills) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Adamos486 Skills Golang CLI Review