cli-audit-shelllisted

Audit shell scripts against Google Shell Style Guide + ops best practices. Scores 12 dimensions: strict mode coherence, error surfaces, logging, stderr hygiene, variable discipline, quoting, control flow, naming, CLI ergonomics, idempotency, namespace, and security. Goes beyond shellcheck — detects semantic anti-patterns invisible to linters (dead fallbacks under set -e, custom loggers vs logger(1), redundant package checks, env var injection in heredocs, missing getopts). Use when reviewing shell scripts, auditing bash code, checking deployment scripts, or saying 'audit shell', 'bash review', 'script quality', 'shell style', 'shellcheck not enough', 'review my script'. Also triggers on 'set -euo pipefail', 'getopts', 'shell injection', 'logger', 'bash best practices', 'google shell style'.
Destynova2/cli-code-skills · ★ 4 · Code & Development · score 83

Install: claude install-skill Destynova2/cli-code-skills

> **Optimization:** This skill uses on-demand loading. Heavy content lives in `references/` and is loaded only when needed. > **Language rule:** Skill instructions are written in English. This skill targets Bash scripts exclusively. When generating user-facing output, detect the project's primary language (from README, comments, docs, commit messages) and produce the report in that language. If the project is bilingual, ask the user which language to use before proceeding. # Audit Shell — Shell Quality Index (SQI) > "Shell should only be used for small utilities or simple wrapper scripts." — Google Shell Style Guide ## Core Principles 1. **Evidence-based** — every finding needs a `file:line` reference. No vague "the script could be better" 2. **Proportional** — a 500-line script doing LVM partitioning matters more than a 10-line wrapper. Scale to script complexity 3. **Beyond shellcheck** — shellcheck catches syntax; this skill catches **semantic** anti-patterns (dead code under `set -e`, redundant package checks, injections in heredocs) 4. **Named anti-patterns** — use the anti-pattern names from `references/anti-patterns.md` in findings 5. **Positive reinforcement** — always highlight good practices found 6. **Complexity-adapted tooling** — simple problems deserve simple tools (sed), complex problems deserve proper tools (kustomize). Read `references/tooling-ladder.md` 7. **Gotchas** — read `../../gotchas.md` before producing output to avoid known mistakes ## Input `