Claude Skill

shellcheck-fix

Run shellcheck on the shipped/installer shell scripts and fix findings while preserving bash 3.2 compatibility. Use after editing any .sh file.

LLM Mart · 0 points · 2 views 0 listing impressions 0 install-command copies
Download dailybothq-deepworkplan-skill-.agents_skills_shellcheck-fix-e516dd0.zip · 0 KB

Install

skills CLI npx skills add https://github.com/DailybotHQ/deepworkplan-skill/tree/main/.agents/skills/shellcheck-fix
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install dailybothq-deepworkplan-skill@llmmart
Git git clone https://github.com/DailybotHQ/deepworkplan-skill.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole dailybothq/deepworkplan-skill collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Shellcheck Fix

Goal

Keep setup.sh, skills/deepworkplan/shared/context.sh, and scripts/*.sh shellcheck-clean and runnable on macOS's default bash 3.2.

When to use

After editing any shell script, or when CI's shellcheck step fails.

Steps

  1. Run shellcheck setup.sh skills/deepworkplan/shared/context.sh scripts/*.sh.
  2. Fix each finding. When resolving, keep the script bash 3.2-safe:
    • replace mapfile/readarray with while IFS= read -r line; do …; done < <(cmd)
    • replace declare -A with a restructured approach
    • replace ${var^^}/${var,,} with tr '[:lower:]' '[:upper:]'
  3. Confirm each script starts with #!/usr/bin/env bash then set -euo pipefail.
  4. Re-run shellcheck until clean.
  5. If setup.sh changed, smoke-test it: HOME="$(mktemp -d)" ./setup.sh --host claude.

Validation

shellcheck setup.sh skills/deepworkplan/shared/context.sh scripts/*.sh exits 0, and the installer smoke test still creates the expected symlinks.

Notes

Do not change setup.sh public flags (--host, --help) or symlink names without flagging a MAJOR bump. CI runs the smoke job on Ubuntu and macOS.

Files (deepworkplan-skill)
  • SKILL.md 1.4 KB
    ---
    name: shellcheck-fix
    description: Run shellcheck on the shipped/installer shell scripts and fix findings while preserving bash 3.2 compatibility. Use after editing any .sh file.
    version: "1.0.0"
    documentation_url: https://deepworkplan.com
    user-invocable: true
    allowed-tools: Bash, Read, Grep, Glob, Edit
    ---
    
    # Shellcheck Fix
    
    ## Goal
    
    Keep `setup.sh`, `skills/deepworkplan/shared/context.sh`, and `scripts/*.sh`
    shellcheck-clean and runnable on macOS's default bash 3.2.
    
    ## When to use
    
    After editing any shell script, or when CI's shellcheck step fails.
    
    ## Steps
    
    1. Run `shellcheck setup.sh skills/deepworkplan/shared/context.sh scripts/*.sh`.
    2. Fix each finding. When resolving, keep the script **bash 3.2-safe**:
       - replace `mapfile`/`readarray` with `while IFS= read -r line; do …; done < <(cmd)`
       - replace `declare -A` with a restructured approach
       - replace `${var^^}`/`${var,,}` with `tr '[:lower:]' '[:upper:]'`
    3. Confirm each script starts with `#!/usr/bin/env bash` then `set -euo pipefail`.
    4. Re-run shellcheck until clean.
    5. If `setup.sh` changed, smoke-test it: `HOME="$(mktemp -d)" ./setup.sh --host claude`.
    
    ## Validation
    
    `shellcheck setup.sh skills/deepworkplan/shared/context.sh scripts/*.sh` exits 0,
    and the installer smoke test still creates the expected symlinks.
    
    ## Notes
    
    Do not change `setup.sh` public flags (`--host`, `--help`) or symlink names
    without flagging a MAJOR bump. CI runs the smoke job on Ubuntu **and** macOS.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.