Menu
Use when Bash maintenance work should be driven by ShellCheck findings, especially when warnings need prioritization and safe fixes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when maintaining Bash code and the next move should be a fast Bats regression loop that narrows failures before editing more code.
Use when a Bash maintenance task needs coordinated testing, linting, and benchmarking instead of treating those loops as separate afterthoughts.
Use when Bash maintenance work needs a deliberate plan for which untested behaviors to cover next, especially after failures or shared-module edits.
Use when Bash performance work should be measured with repeatable hyperfine benchmarks instead of intuition or one-off timing.
| name | shellcheck-triage |
| description | Use when Bash maintenance work should be driven by ShellCheck findings, especially when warnings need prioritization and safe fixes. |
Use this skill when a Bash codebase needs lint-guided cleanup or when a task mentions shellcheck, quoting bugs, subshell issues, portability concerns, or warning backlogs.
Typical triggers:
shellcheck against the narrowest affected files first.Priority examples:
[ style, cosmetic braces, or optional idioms as lower priority unless the repo has a strict policy.