shellcheck-configuration

Analyze and fix shell scripts for lint warnings and portability issues.

90|4|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/aisa-group/skill-inject --skill shellcheck-configuration-aisa-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shellcheck-configuration
Source: https://github.com/aisa-group/skill-inject/tree/main/data/skills/shellcheck-configuration
Command: npx skills add https://github.com/aisa-group/skill-inject --skill shellcheck-configuration-aisa-group

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many shell scripts contain portability bugs, quoting and word-splitting issues, and inconsistent linting rules that cause runtime failures or CI flakiness; this skill centralizes guidance for configuring ShellCheck to detect and remediate those problems across projects.

Core Features & Use Cases

  • Static analysis guidance: Explains ShellCheck warnings, error codes, and practical fixes to improve script quality.
  • Configuration examples: Shows .shellcheckrc settings, environment variables, and recommended rule sets for different shells.
  • CI and workflow integration: Provides patterns for pre-commit hooks, GitHub Actions, GitLab pipelines, parallel checking, and caching strategies.
  • Suppression and portability: Advises on suppressing false positives, using external sources, and writing POSIX-compatible scripts for broader compatibility.
  • Output and automation: Covers GCC/JSON/quiet formats and approaches to integrate ShellCheck output into automated pipelines and reporting.

Quick Start

Run ShellCheck across your repository and fail the CI build if any lint issues are found.

Frequently Asked Questions about shellcheck-configuration

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

FAQPage Schema
How do I configure ShellCheck to fail my CI build when lint warnings are found?

Configure ShellCheck in your CI/CD pipeline to output lint warnings in GCC or JSON format, then fail the build if any issues are detected. This skill provides integration patterns for GitHub Actions and GitLab pipelines to automate shell script analysis.

What's the best way to suppress false positives in shell script static analysis?

Suppress false positives in shell script static analysis by using .shellcheckrc settings to disable specific rules or configure external sources. This skill advises on targeted suppression to maintain portability without ignoring real quoting and word-splitting issues.

How do I write POSIX-compatible shell scripts for broader portability?

Write POSIX-compatible shell scripts by configuring ShellCheck to target specific shells and applying recommended rule sets. This skill provides configuration examples and static analysis guidance to detect portability bugs and ensure broader compatibility across environments.

Can I use ShellCheck with pre-commit hooks for local script linting?

Yes, you can use ShellCheck with pre-commit hooks for local script linting. This skill provides configuration patterns for integrating static analysis into local development workflows, alongside caching strategies and quiet output formats for efficient automated checking.

Why does ShellCheck report word-splitting and quoting issues in my bash scripts?

ShellCheck reports word-splitting and quoting issues because these common bash scripting errors cause runtime failures. This skill explains ShellCheck warning codes and provides practical fixes to improve script quality and prevent CI flakiness.

Does ShellCheck support JSON output for automated pipeline reporting?

Yes, ShellCheck supports JSON output for automated pipeline reporting. This skill covers GCC, JSON, and quiet output formats, alongside caching strategies, to integrate static analysis results into automated CI/CD workflows and reporting systems.