How do I set up linting for shell scripts in CI/CD pipelines?

Add a ShellCheck step to the pipeline that runs the tool on your scripts. The skill covers running checks in CI pipelines and using pre-commit hooks to catch issues before pushing.

How do I analyze existing shell scripts for issues?

Run ShellCheck on the scripts and review the reported warnings and errors. The skill explains error codes and how to address violations rather than just disabling warnings.

How do I understand ShellCheck error codes and warnings?

The skill explains ShellCheck error codes and warnings, including how to configure rule sets and suppress false positives with documented exclusions.

ShellCheck Configuration and Static Analysis

SkillAI & models

This skill helps an agent set up and use ShellCheck, a static analysis tool that scans shell scripts for bugs and bad practices. It covers running checks in CI pipelines, targeting the right shell, handling warnings and false positives, and enforcing code quality standards. Use it when setting up linting infrastructure, fixing code issues, or ensuring script portability.

Connect your AI Use it in a pipeline

Then ask your AI: use the ShellCheck Configuration and Static Analysis skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.

No other account needed.

Install ShellCheck on the machine where scripts will be checked.

What your AI can do with it

Set up ShellCheck linting for shell scripts in CI/CD pipelines
Analyze existing shell scripts for issues
Explain ShellCheck error codes and warnings
Configure ShellCheck for specific project requirements
Suppress false positives and configure rule sets
Enforce consistent code quality standards

Getting started

Install ShellCheck on the machine where scripts will be checked.
Decide which shell the scripts target, such as bash or sh, so ShellCheck analyzes them correctly.
Add a ShellCheck step to the CI/CD pipeline or a pre-commit hook.
Run ShellCheck on the scripts and review the reported warnings and errors.
Document any exclusions and fix the remaining violations.

What this skill tells your AI

The instructions your AI receives, as published by wshobson/agents in plugins/shell-scripting/skills/shellcheck-configuration/SKILL.md and read by Ahel’s review.

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

Signals

GitHub stars: 40k
Forks: 4k
Last commit: Oct 2026

Ahel review

K1binfo
installs-packages (in references/details.md)

Automated review, not a security audit. Ruleset v1+k2.

Questions

How do I set up linting for shell scripts in CI/CD pipelines?: Add a ShellCheck step to the pipeline that runs the tool on your scripts. The skill covers running checks in CI pipelines and using pre-commit hooks to catch issues before pushing.
How do I analyze existing shell scripts for issues?: Run ShellCheck on the scripts and review the reported warnings and errors. The skill explains error codes and how to address violations rather than just disabling warnings.
How do I understand ShellCheck error codes and warnings?: The skill explains ShellCheck error codes and warnings, including how to configure rule sets and suppress false positives with documented exclusions.

Advanced

Item type: skill
Key: shellcheck-configuration-wshobson
Source: github.com/wshobson/agents

github.com/wshobson/agents