shellcheck-configuration

Configure ShellCheck static analysis with .shellcheckrc for CI/CD integration.

52|6|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/ovachiever/droid-tings --skill shellcheck-configuration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shellcheck-configuration
Source: https://github.com/ovachiever/droid-tings/tree/main/skills/shellcheck-configuration
Command: npx skills add https://github.com/ovachiever/droid-tings --skill shellcheck-configuration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a robust ShellCheck static analysis workflow to catch common Bash pitfalls, enforce best practices, and integrate linting into CI/CD for portable, reliable scripts.

Core Features & Use Cases

  • Project-level .shellcheckrc and environment variable configurations
  • Common error code guidance and suppression strategies
  • Pre-commit and CI integrations for automated checks
  • Platform-wide portability and POSIX-compliance guidance

Quick Start

Add a .shellcheckrc to your repo, run shellcheck on your scripts, and integrate into a CI workflow.

Frequently Asked Questions about shellcheck-configuration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up ShellCheck linting for my bash scripts in a CI/CD pipeline?

ShellCheck is a static analysis tool that catches common bash errors and portability issues. Create a .shellcheckrc file in your repo to configure rules, install ShellCheck cross-platform, then integrate it into GitHub Actions, GitLab CI, or pre-commit hooks to automatically lint scripts on commit or push.

What does ShellCheck detect and how do I suppress false positives?

ShellCheck identifies bash pitfalls, POSIX compliance violations, and unsafe patterns using error codes. Suppress specific warnings inline with `# shellcheck disable=SC####` comments or globally in .shellcheckrc using the disable directive to reduce noise from false positives.

Can I use ShellCheck to check bash compatibility across different shells?

Yes. ShellCheck validates portability across Bash, sh, dash, and POSIX shells. Configure target shells in .shellcheckrc or via environment variables to enforce compliance rules specific to your deployment platforms.

How do I integrate ShellCheck into pre-commit hooks?

Add a pre-commit hook configuration that runs ShellCheck on staged shell files before each commit. This catches linting issues locally during development, reducing review cycles and preventing non-compliant scripts from reaching CI.

What configuration options does ShellCheck support for project-level setup?

ShellCheck supports project-level configuration through .shellcheckrc files and environment variables to control enabled checks, exclude patterns, and target shell dialects, enabling consistent linting across team workflows without per-command flags.

Is ShellCheck suitable for migrating legacy bash scripts to POSIX compliance?

Yes. ShellCheck's portability and POSIX compliance checks help identify non-portable constructs in legacy scripts, guiding incremental migration to standards-compliant code across heterogeneous deployment environments.