shellcheck-skill

Lint Bash, Dash, and POSIX shell scripts with ShellCheck warnings and fixes.

3|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/jbovet/oxidized-agentic-audit --skill shellcheck-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shellcheck-skill
Source: https://github.com/jbovet/oxidized-agentic-audit/tree/main/tests/fixtures/shellcheck-skill
Command: npx skills add https://github.com/jbovet/oxidized-agentic-audit --skill shellcheck-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Shell scripting mistakes and unsafe patterns often slip into code, leading to runtime errors and security vulnerabilities. This Skill uses ShellCheck to identify common issues, misconfigurations, and portability problems in shell scripts.

Core Features & Use Cases

  • Lints Bash, Dash, and other POSIX-compatible scripts using ShellCheck warnings and recommended fixes.
  • Highlights common pitfalls (unquoted variables, word splitting, array handling) to improve script robustness.
  • Suitable for CI pipelines and local development to enforce scripting best-practices and reduce bugs before deployment.

Quick Start

Scan all shell scripts in your project with the shellcheck-skill to surface warnings and suggested improvements.

Frequently Asked Questions about shellcheck-skill

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

FAQPage Schema
How do I automatically detect and fix shellcheck issues in my bash scripts?

To detect and fix shellcheck issues in bash scripts, you can lint POSIX-compatible scripts across project directories to identify common warnings and apply recommended corrections for unsafe patterns like unquoted variables.

Can I lint shell scripts for common pitfalls like word splitting in a CI workflow?

Yes, you can lint shell scripts in CI workflows to enforce scripting best-practices by highlighting portability problems and common pitfalls such as word splitting and array handling before deployment.

What is the best way to find security vulnerabilities in my shell scripts before deployment?

Finding security vulnerabilities in shell scripts involves applying ShellCheck rules to identify misconfigurations and unsafe patterns, providing recommended fixes to improve script robustness and reduce runtime errors.

Does this shell script linting approach work with POSIX-compatible scripts like Dash?

Yes, this shell script linting approach works with Dash and other POSIX-compatible scripts by applying ShellCheck warnings and recommended fixes across individual scripts or entire project directories.

Why does my shell script fail in CI due to unquoted variable warnings?

Shell scripts fail in CI due to unquoted variable warnings because linting tools identify word splitting and unsafe patterns, providing recommended fixes to improve script robustness and enforce best-practices.

What are the limitations of using ShellCheck to remediate shell scripting issues?

Using ShellCheck to remediate shell scripting issues is limited to detecting common warnings, misconfigurations, and portability problems in POSIX-compatible scripts, focusing on known unsafe patterns rather than complex runtime logic.