shellcheck-configuration — Claude Code skill: use and install
This skill guides ShellCheck setup and use for shell script analysis. Use it when adding CI/CD linting, fixing warnings, or checking script portability.
/plugin marketplace add wshobson/agents
/plugin install shell-scripting@claude-code-workflowsWhat shellcheck-configuration does
shellcheck-configuration helps apply ShellCheck to shell scripts, find common issues, understand warning codes, and set rules for a project. It covers linting in CI/CD, pre-commit hooks, editors, and development workflows.
The skill explains how to select the target shell, document exclusions for false positives, and use --enable=all with careful exceptions. Detailed patterns and worked examples are available in references/details.md when the basic navigation is not enough.
Install it when a project contains shell scripts and needs explicit static-analysis rules. Before using it, decide which shell each script targets and record why any warning is suppressed.
What it helps with
- add ShellCheck linting to CI/CD
- interpret ShellCheck warning and error codes
- configure rules for bash or sh scripts
- document exclusions for false positives
- connect script checks to pre-commit hooks or an editor
Example prompts for the agent
- Run ShellCheck on the project’s shell scripts and group the warnings by type.
- Configure ShellCheck for the target shell, then document the exclusions for false positives.
- Add ShellCheck to CI/CD and enable `--enable=all` with carefully chosen exceptions.
How to install shellcheck-configuration
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install shell-scripting@claude-code-workflowsThis installs the whole shell-scripting plugin with all its skills
2Skills CLI (Vercel)
npx skills add wshobson/agents --skill shellcheck-configuration -a claude-code3Manually: put the files in place
~/.claude/skills/shellcheck-configuration/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/shellcheck-configuration/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill shellcheck-configuration -a codex2Manually: put the files in place
.agents/skills/shellcheck-configuration/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill shellcheck-configuration -a cursor2Manually: put the files in place
.cursor/skills/shellcheck-configuration/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wshobson/agents shellcheck-configuration2Manually: put the files in place
.github/skills/shellcheck-configuration/SKILL.mdPlatform CLI
gemini skills install https://github.com/wshobson/agents --path plugins/shell-scripting/skills/shellcheck-configurationManually: put the files in place
.devin/skills/shellcheck-configuration/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set213
The whole set →Similar
Questions about shellcheck-configuration
How do I install shellcheck-configuration in Claude Code?
Run npx skills add wshobson/agents --skill shellcheck-configuration -a claude-code. The skill file is placed at ~/.claude/skills/shellcheck-configuration/SKILL.md.
What does shellcheck-configuration do?
It guides ShellCheck setup, shell script analysis, and warning review. It also covers CI/CD, pre-commit hooks, editor integration, and project-specific rule sets.
How should ShellCheck be configured for a project?
Set the target shell first, because bash should not be analyzed as sh. Then choose the rule set, document exclusions, and use --enable=all with deliberate exceptions when appropriate.
Source text
SKILL.md · MIT
--- name: shellcheck-configuration description: Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability. --- # ShellCheck Configuration and Static Analysis Comprehensive guidance for configuring and using ShellCheck to improve shell script quality, catch common pitfalls, and enforce best practices through static code analysis. ## When to Use This Skill - Setting up linting for shell scripts in CI/CD pipelines - Analyzing existing shell scripts for issues - Understanding ShellCheck error codes and warnings - Configuring ShellCheck for specific project requirements - Integrating ShellCheck into development workflows - Suppressing false positives and configuring rule sets - Enforcing consistent code quality standards - Migrating scripts to meet quality gates ## Detailed patterns and worked examples Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient. ## Best Practices 1. **Run ShellCheck in CI/CD** - Catch issues before merging 2. **Configure for your target shell** - Don't analyze bash as sh 3. **Document exclusions** - Explain why violations are suppressed 4. **Address violations** - Don't just disable warnings 5. **Enable strict mode** - Use `--enable=all` with careful exclusions 6. **Update regularly** - Keep ShellCheck current for new checks 7. **Use pre-commit hooks** - Catch issues locally before pushing 8. **Integrate with editors** - Get real-time feedback during development
© Ryan Snodgrass · MIT · wshobson/agents