mcpbeat

Shellcheck Configuration

wshobson/shellcheck-configuration

Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.

2k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
38452
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/wshobson/agents --skill shellcheck-configuration

The instruction itself

4 sections, as written by the author

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

How to use it

Copy the folder

Take wshobson/shellcheck-configuration from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.