agentleFS
Sign inStart free
CassetteTapeCrackleCassetteTapeCrackle/claude-starters/skills/clean-code-bash/SKILL.md

clean-code-bash

Skill1 starsChanged 3 months agoMITView on GitHub

Use when writing or reviewing shell scripts — deeper idioms (strict mode, quoting, traps, arrays, safe substitution, exit codes) beyond a shellcheck pass.

  • Deletes or force-pushes

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Read lines with while IFS= read -r line or mapfile.

    line 17

≈ “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

Clean-code Bash (depth)

On top of the base rules (set -euo pipefail, shellcheck clean, bats tests).

Safety

  • set -euo pipefail always; understand where -e doesn't fire (in if, ||, command substitution) and check explicitly there.
  • Quote every expansion; "${arr[@]}" for arrays. [[ ]] for tests; (( )) for arithmetic.
  • trap 'rm -rf "$tmp"' EXIT for cleanup; create temps with mktemp -d.

Robustness

  • local all function vars. Prefer functions + a main "$@" entrypoint.
  • Read lines with while IFS= read -r line or mapfile; never parse ls.
  • Parameter expansion for defaults/checks: "${VAR:?message}", "${VAR:-default}".
  • printf '%s\n' over echo for arbitrary data. Meaningful exit codes; errors to stderr (>&2).

Smells

  • Unquoted $var in a path/test → word-splitting/glob bug.
  • Parsing ls/find output by whitespace → use globs or -print0/read -d ''.
  • A temp file with no trap cleanup → litter on failure.

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