How do I install the Shellcheck Configuration skill?

Run npx skillmds@latest add wshobson/shellcheck-configuration-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Shellcheck Configuration safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Shellcheck Configuration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Shellcheck Configuration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Shellcheck Configuration?

wshobson (@wshobson) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Shellcheck Configuration by wshobson

Name: Shellcheck Configuration
Rating: 4.2 (5 reviews)
Author: wshobson

File contents

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

Run ShellCheck in CI/CD - Catch issues before merging
Configure for your target shell - Don't analyze bash as sh
Document exclusions - Explain why violations are suppressed
Address violations - Don't just disable warnings
Enable strict mode - Use --enable=all with careful exclusions
Update regularly - Keep ShellCheck current for new checks
Use pre-commit hooks - Catch issues locally before pushing
Integrate with editors - Get real-time feedback during development

Source: wshobson/agents → plugins/shell-scripting/skills/shellcheck-configuration/SKILL.md

--- name: shellcheck-configuration-2 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." category: engineering-core source_repo: wshobson/agents source_path: "plugins/shell-scripting/skills/shellcheck-configuration/SKILL.md" source_url: https://github.com/wshobson/agents/blob/HEAD/plugins/shell-scripting/skills/shellcheck-configuration/SKILL.md --- # 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 --- **Source:** [`wshobson/agents`](https://github.com/wshobson/agents) → `plugins/shell-scripting/skills/shellcheck-configuration/SKILL.md`

Frequently asked questions

Shellcheck Configuration