Back to Skills

shellck

Run shellcheck on shell scripts after editing scripts or when debugging shell errors. Use for linting scripts in a repo (especially scripts/), catching issues like set -u with unset vars, bad subshell usage, or quoting mistakes.

43stars5forksUpdated 4/3/2026

Security Assessment

Safe(100/100)
Security Score100/100

About shellck

The shellck skill provides a streamlined and repeatable method for running shellcheck on shell scripts within a repository. It is designed to assist developers in identifying and correcting common shell scripting errors, such as using unset variables with 'set -u', improper quoting, or incorrect subshell usage. By automating the linting process, shellck helps maintain consistent code quality and reduces the likelihood of runtime errors, especially in scripts that are frequently modified or critical to automated workflows.

This skill features a helper script that can be executed from the repository root. By default, it scans the 'scripts/' directory, but it also accepts specific files or directories as arguments. The tool intelligently filters targets based on file extensions or shebang lines to ensure only shell scripts are analyzed. It exits with a non-zero status when issues are detected, providing immediate feedback. The skill relies on the presence of shellcheck, making installation a prerequisite, but otherwise requires minimal configuration. The included runner script is designed with sensible defaults, allowing users to quickly incorporate it into their development workflow.

Shellck is ideal for developers and DevOps engineers who regularly write or maintain shell scripts and want to catch errors early. It is particularly useful in collaborative environments where multiple contributors edit scripts, as it enforces consistent best practices. Common use cases include verifying scripts after editing, performing pre-commit checks, debugging failing scripts, or integrating into CI/CD pipelines to automate quality checks. Its simplicity and focus on shell scripts make it a practical tool for anyone seeking to improve script reliability and maintainability.

FAQ

How do I run shellck on my scripts?

Execute the included helper script from the repository root. By default, it scans the 'scripts/' directory, but you can specify files or directories as arguments.

What are the prerequisites for using shellck?

You must have shellcheck installed on your system. No additional configuration is required for the basic workflow.

Can shellck scan individual files as well as directories?

Yes, you can provide specific files or directories. The skill filters targets to shell scripts based on file extensions or shebang lines.

What happens if shellcheck detects errors?

The helper script exits with a non-zero status, indicating that issues were found, allowing you to take corrective action.

Is shellck suitable for automated CI/CD pipelines?

Yes, shellck can be incorporated into CI/CD workflows to perform automated linting and ensure script quality before deployment.

Install shellck

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill