agentleFS
Sign inStart free
DailybotHQDailybotHQ/deepworkplan-skill/.agents/skills/shellcheck-fix/SKILL.md

shellcheck-fix

Skill23 starsChanged 5 months agoMITView on GitHub

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

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

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

    line 14
  2. Distinctive:

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

    line 19
  3. Very specific:

    If setup.sh changed, smoke-test it: HOME="$(mktemp -d)" ./setup.sh --host claude.

    line 30
  4. Very specific:

    Do not change setup.sh public flags (--host, --help) or symlink names without flagging a MAJOR bump.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free