shellck

Lint shell scripts with shellcheck and exit non-zero on issues.

131|13|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/regenrek/agent-skills --skill shellck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shellck
Source: https://github.com/regenrek/agent-skills/tree/main/skills/shellck
Command: npx skills add https://github.com/regenrek/agent-skills --skill shellck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires shellcheck, and includes scripts (resource) components.

What problem does it solve?

Shell scripts frequently accumulate linting issues that can cause runtime errors, security concerns, or maintainability problems. shellck provides fast, repeatable linting by running shellcheck on edited or targeted scripts to catch common mistakes such as unset variables, unsafe subshell usage, and quoting errors.

Core Features & Use Cases

  • Automatic detection of shell scripts by file extension or shebang and linting with shellcheck.
  • Works from the repository root on the default scripts/ directory or on user-specified files or directories, returning actionable feedback on issues.
  • Exits with non-zero status when shellcheck reports problems, enabling automation, CI checks, and gated deployments.

Quick Start

From the repository root, run the shellck helper to lint the scripts directory.

Frequently Asked Questions about shellck

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

FAQPage Schema
How do I lint shell scripts for unsafe patterns and quoting errors?

Lint shell scripts by running shellcheck on targeted files or the default scripts/ directory to catch unset variables, unsafe subshell usage, and quoting errors. It detects scripts by extension or shebang and returns actionable feedback on issues.

What is static analysis for shell scripts and when do I need it?

Static analysis for shell scripts scans code to identify common mistakes like unsafe subshell usage and quoting errors before runtime. You need it when shell scripts accumulate issues that cause runtime errors, security concerns, or maintainability problems.

Do I need shellcheck installed to lint scripts in my repository?

Yes, you need shellcheck installed to lint scripts in your repository. The tool requires shellcheck to be installed locally to scan the scripts/ directory or user-specified paths for errors and unsafe patterns.

Can I use shell script linting for CI checks and gated deployments?

Yes, you can use shell script linting for CI checks and gated deployments. The tool exits with a non-zero status when shellcheck reports problems, enabling automation and preventing deployments when errors are detected.

How do I scan specific files or directories instead of the default scripts folder?

Scan specific files or directories by providing user-specified paths to the linting tool. By default it works from the repository root on the scripts/ directory, but you can target custom paths to identify shell scripting issues across repositories.