agentleFS
aquahittaquahitt/claude-code-limit-alerts/.claude/skills/check-scripts/SKILL.md

check-scripts

Skill1 starsChanged 4 months agoMITView on GitHub

Run the full shell quality gate (bash -n + shellcheck) before commit — this project has no test framework, this is the whole gate

  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. vladmandic/sdnext★ 7.4ksame name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

Files
SKILL.md

Check Scripts

This project is pure bash with no test runner. This is the entire quality gate before a commit.

  • Syntax — all changed *.sh files parse cleanly:
    git diff --name-only --diff-filter=ACM HEAD -- '*.sh' | xargs -I{} bash -n {}
  • shellcheck (if installed — brew install shellcheck; if not, skip this step and say so explicitly, don't pretend it passed):
    git diff --name-only --diff-filter=ACM HEAD -- '*.sh' | xargs shellcheck -S warning
    Existing code may not be idiomatically shellcheck-clean — focus on new/changed lines, don't rewrite unrelated chunks just to satisfy the linter.
  • Manual behavior check. There are no automated tests — wherever logic in install.sh/uninstall.sh/update.sh/lib/hooks.sh changed, exercise it with real commands and expected output. Edits that touch ~/.claude/settings.json or launchd should be done with an overridden HOME (sandboxed), never against the real environment:
    env -i HOME=/tmp/fake-home PATH=/usr/bin:/bin:/usr/sbin:/sbin bash -c '...'
  • If install.sh/uninstall.sh/update.sh/lib/hooks.sh changed — consider the installer-safety-reviewer skill/agent for idempotency and safety around editing the user's settings.json.

All green?

Commit.

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.