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
What this skill does
# 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 in Security
mac-ops
IncludedComprehensive macOS workstation operations — diagnose kernel panics, identify failing drives, audit launchd startup items, decode wake reasons, triage TCC permission denials, manage APFS snapshots, recover from no-boot. Use for: Mac is slow, slow bootup, won't boot, kernel panic, kernel_task hot, mds_stores CPU, photoanalysisd, cloudd, login loop, gray screen, sleep wake failure, drive failing, IO errors, APFS snapshots eating space, Time Machine local snapshots, Spotlight indexing, launchd, LaunchAgent, LaunchDaemon, login items, TCC permissions, Full Disk Access, Screen Recording denied, Gatekeeper, quarantine, com.apple.quarantine, app is damaged, helper tool, /Library/PrivilegedHelperTools, pmset, wake reasons, dark wake, sysdiagnose, panic.ips, DiagnosticReports, configuration profile, MDM profile, remote diagnostics over SSH.
a11y-audit
IncludedRun accessibility audits on web projects combining automated scanning (axe-core, Lighthouse) with WCAG 2.1 AA compliance mapping, manual check guidance, and structured reporting. Output is configurable: markdown report only, markdown plus machine-readable JSON, or markdown plus issue tracker integration. Use this skill whenever the user mentions "accessibility audit", "a11y audit", "WCAG audit", "accessibility check", "compliance scan", or asks to check a web project for accessibility issues. Also trigger when the user wants to verify WCAG conformance or map findings to a specific standard (CAN-ASC-6.2, EN 301 549, ADA/AODA).
erpclaw
IncludedAI-native ERP system with self-extending OS. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting. 413 actions across 14 domains, 43 expansion modules. Constitutional guardrails, adversarial audit, schema migration. Double-entry GL, immutable audit trail, US GAAP.
assess
IncludedAssesses and rates quality 0-10 across multiple dimensions (correctness, maintainability, security, performance, testability, simplicity) with pros/cons analysis. Compares against project conventions and prior decisions from memory. Produces structured evaluation reports with actionable improvement suggestions. Use when evaluating code, designs, architectures, or comparing alternative approaches.
spring-boot-security-jwt
IncludedProvides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based access control using Spring Security 6.x. Use when implementing authentication or authorization in Spring Boot applications.
code-hardcode-audit
IncludedDetect hardcoded values, magic numbers, and leaked secrets. TRIGGERS - hardcode audit, magic numbers, PLR2004, secret scanning.