shellcheck-configuration
Configure ShellCheck for reliable shell linting
Shell script issues hide until production and slow code reviews. This skill explains ShellCheck setup, rule configuration, and integration workflows to catch problems before merge.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "shellcheck-configuration". I need help understanding SC2086 and how to fix it
Expected outcome:
- SC2086 is the unquoted variable expansion warning
- Fix by quoting variables or using array syntax
- Example: change 'for i in $list' to 'for i in "$list"' or 'for i in "${list[@]}"'
Using "shellcheck-configuration". Create a .shellcheckrc for a Bash project
Expected outcome:
- Set shell=bash for Bash dialect analysis
- Enable optional checks like require-variable-braces
- Disable SC1091 for sourced files that may not exist
- Document each disabled code with a comment explaining why
Security Audit
SafePure documentation skill containing only markdown guidance for ShellCheck, a legitimate open-source static analysis tool. All static findings are false positives. References like SC2009, SC2086 are ShellCheck error codes (not C2 keywords), sha256sum is appropriate for caching (not weak crypto), and shell examples are documentation (not malicious patterns).
Risk Factors
🌐 Network access (5)
⚙️ External commands (72)
📁 Filesystem access (5)
Quality Score
What You Can Build
Add CI shell linting
Set up ShellCheck in CI pipelines with consistent flags and failure rules.
Fix common warnings
Understand key ShellCheck codes and apply safer quoting and flow patterns.
Standardize lint rules
Define shared .shellcheckrc settings and documented suppression policies.
Try These Prompts
Explain how to install ShellCheck and run it on a single script. Include example commands for installing on Ubuntu and running against a Bash file.
Draft a .shellcheckrc for Bash scripts with a few enabled checks and two disabled codes. Explain each setting.
Provide a minimal GitHub Actions step that installs ShellCheck and runs it on all .sh files, failing on warnings.
Show how to suppress SC1091 and SC2119 in a shell script and document why each suppression is safe.
Best Practices
- Set the target shell explicitly before linting to match your deployment environment
- Document every suppressed code with a comment explaining the justification
- Run ShellCheck in both pre-commit hooks and CI for early local and remote detection
Avoid
- Disable warnings broadly without specific justification for each code
- Lint Bash scripts as POSIX sh without understanding compatibility requirements
- Ignore ShellCheck failures in CI or override exit codes without review
Frequently Asked Questions
Is this compatible with Bash and POSIX sh?
What are the limits of this skill?
Can it integrate with CI systems?
Does it access my files or credentials?
What if ShellCheck reports too many warnings?
How does it compare to generic linters?
Developer Details
Author
wshobsonLicense
MIT
Repository
https://github.com/wshobson/agents/tree/main/plugins/shell-scripting/skills/shellcheck-configurationRef
main
File structure
📄 SKILL.md