ShellCheck Configuration and Static Analysis
Unverified●29/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add shellcheck-configurationWho is stuck, and on what
Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.
The whole source
Frontmatter — 2 properties
| 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. |
| 1 | --- |
| 2 | name: shellcheck-configuration |
| 3 | 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. |
| 4 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 5 | |
| 6 | # ShellCheck Configuration and Static Analysis |
| 7 | |
| 8 | Comprehensive guidance for configuring and using ShellCheck to improve shell script quality, catch common pitfalls, and enforce best practices through static code analysis. |
| 9 | |
| 10 | ## When to Use This Skill |
| 11 | |
| 12 | - Setting up linting for shell scripts in CI/CD pipelines |
| 13 | - Analyzing existing shell scripts for issues |
| 14 | - Understanding ShellCheck error codes and warnings |
| 15 | - Configuring ShellCheck for specific project requirements |
| 16 | - Integrating ShellCheck into development workflows |
| 17 | - Suppressing false positives and configuring rule sets |
| 18 | - Enforcing consistent code quality standards |
| 19 | - Migrating scripts to meet quality gates |
| 20 | |
| 21 | ## Detailed patterns and worked examples |
| 22 | |
| 23 | Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient. |
| 24 | |
| 25 | ## Best Practices |
| 26 | |
| 27 | 1. **Run ShellCheck in CI/CD** - Catch issues before merging |
| 28 | 2. **Configure for your target shell** - Don't analyze bash as sh |
| 29 | 3. **Document exclusions** - Explain why violations are suppressed |
| 30 | 4. **Address violations** - Don't just disable warnings |
| 31 | 5. **Enable strict mode** - Use `--enable=all` with careful exclusions |
| 32 | 6. **Update regularly** - Keep ShellCheck current for new checks |
| 33 | 7. **Use pre-commit hooks** - Catch issues locally before pushing |
| 34 | 8. **Integrate with editors** - Get real-time feedback during development |
| 35 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Subagent Driven DevelopmentUse when executing implementation plans with independent tasks in the current session◐◐◐◐◐●36/40Python Code Style & DocumentationPython code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.◐····●35/40Competitor Price Analysis 💲Competitor pricing strategy analysis and market positioning. Price mapping, pricing gaps identification, elasticity signals evaluation, and strategic pricing optimization. Use when the user asks about competitor pricing, price analysis, pricing strategy, or co◐····●34/40Competitor Price Tracker 📊Set up competitor price tracking and monitoring workflows. Track price changes, detect promotions, analyze pricing patterns, and get alerts for competitive price movements.◐····●34/40