bash-script-quality

Validate edited Bash scripts with shellcheck until zero issues remain.

12|1|Updated Jun 4, 2013

Search Tags:#automation #devops #bash #shellcheck #code-quality #lint #script-quality

Ready to run

npx skills add https://github.com/bostonaholic/dotfiles --skill bash-script-quality

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bash-script-quality
Source: https://github.com/bostonaholic/dotfiles/tree/main/claude/skills/bash-script-quality
Command: npx skills add https://github.com/bostonaholic/dotfiles --skill bash-script-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that every Bash script edit is validated with shellcheck to catch syntax and stylistic issues before they reach production.

Core Features & Use Cases

Always run shellcheck after editing any Bash script to detect errors and warnings.
Enforce a repeatable quality workflow by requiring fixes for all issues (including pre-existing) before proceeding.
Suitable for local development, code reviews, and CI pipelines to maintain Bash script integrity.

Quick Start

Run shellcheck on the edited script and fix all issues until shellcheck reports zero errors.

Frequently Asked Questions about bash-script-quality

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

FAQPage Schema

How do I automate shellcheck validation for Bash scripts after every edit?▼

Automate shellcheck validation by running it after every Bash script edit to catch syntax and stylistic issues early. This enforces a repeatable workflow that reports all errors and warnings, stopping only when zero issues remain.

What's the best way to enforce Bash script quality in a CI pipeline?▼

Enforce Bash script quality in a CI pipeline by running shellcheck to validate scripts after edits. This requires fixing all reported errors and warnings, ensuring zero issues remain before proceeding to production.

Can I use shellcheck linting for local Bash script development?▼

Yes, you can use shellcheck linting for local Bash script development. Running shellcheck after each edit detects syntax and stylistic issues immediately, enforcing a repeatable quality workflow before code reaches production.

Does shellcheck validation require fixing pre-existing Bash script warnings?▼

Yes, shellcheck validation requires fixing pre-existing warnings. The workflow enforces a repeatable quality standard by requiring fixes for all reported issues, including pre-existing errors, before allowing you to proceed.

How does automated shellcheck linting improve shell script code reviews?▼

Automated shellcheck linting improves shell script code reviews by detecting syntax and stylistic issues after edits. It enforces a repeatable workflow that requires zero shellcheck errors and warnings before proceeding.

When do I need to run shellcheck on my Bash scripts?▼

You need to run shellcheck on your Bash scripts after every edit to catch syntax and stylistic issues early. This applies to local development, code reviews, and CI pipelines to maintain script integrity.