One-click install
npx skills add https://github.com/shiiman/dotfiles --skill lint-shiiman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/shiiman/dotfiles/tree/main/.claude/skills/lint
Command: npx skills add https://github.com/shiiman/dotfiles --skill lint-shiiman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shell scripts often contain shellcheck warnings that can go unnoticed. This skill runs shellcheck on targeted scripts and suggests fixes to improve reliability and portability.

Core Features & Use Cases

  • Run shellcheck on one or more .sh files to identify warnings and potential issues.
  • Propose automatic fixes or guided suggestions to resolve common shell scripting pitfalls.
  • Use cases include validating new scripts before commit, auditing a repository for shell errors, and enforcing coding standards.

Quick Start

Run lint on your shell scripts by specifying the path to the script you want checked.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I run shellcheck on shell scripts and automatically apply fixes?

To run shellcheck and apply fixes, you can process staged or unstaged .sh files using the --fix mode to automatically resolve warnings and generate actionable lint reports.

What is the best way to lint bash scripts before a git commit?

The best way to lint bash scripts before a commit is to run static analysis on targeted paths or staged .sh files, identifying potential issues and enforcing coding standards before submission.

Do I need shellcheck installed to lint my shell scripts?

Yes, you need shellcheck installed locally to lint shell scripts, as the tool relies on it to identify warnings and provide actionable suggestions for your code.

Can I check specific file paths for shellcheck warnings without fixing them?

Yes, you can check specified paths for shellcheck warnings without altering them by using the --check mode to produce a detailed lint report of potential issues.

How does static analysis improve shell script reliability and portability?

Static analysis improves shell script reliability by detecting common shellcheck warnings and suggesting fixes, helping you avoid scripting pitfalls and ensure cross-platform compatibility.

Why are my shell scripts failing in production despite passing manual reviews?

Shell scripts often fail because manual reviews miss shellcheck warnings, so running automated static analysis with --check mode can identify hidden issues and propose fixes for better reliability.