golang-cli-review
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
More from adamos486/skills
song-lyrics
Provides insights and techniques from renowned songwriters across different genres to help users improve their own lyrical compositions.
141dadjoke
Provides a curated list of 10+ classic and obscure dad jokes. Use this skill when an AI needs to quickly generate some humorous dad jokes, such as in casual conversation or to lighten the mood.
59production-ready
Use when preparing any project for production deployment, performing security audits, or release preparation. Triggers on "make production ready", "security audit", "prepare for release", "hardening", "pre-deployment checklist".
42superplan
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.
14teach
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.
13superbuild
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.
12