agentleFS
joelbarmettlerUZHjoelbarmettlerUZH/ultrainit.sh/.claude/skills/check-ci-locally/SKILL.md

check-ci-locally

Skill8 starsChanged 7 months agoApache-2.0View on GitHub

This runs: 1. bash -n on all .sh files (excluding ./test-repos/*) 2. jq empty on all schemas/*.json Equivalent manual commands: bash -n failure: Means a syntax error at line 42 of lib/agent.sh. bash -n checks syntax only — it does not execute the script, so functions and variables are not evaluated. jq empty failure: Means schemas/identity.json is not valid JSON. Use python3 -m json.tool schemas/identity.json for a more informative error with line numbers. If you changed any file in lib/,…

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:

    If you changed any file in lib/, prompts/, scripts/, or added new files:

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Before You Start

  • .github/workflows/test.yml — the syntax job (runs before test job)
  • Makefile — check target (mirrors what CI does)

Steps

Run the check

make check

This runs:

  1. bash -n on all .sh files (excluding ./test-repos/*)
  2. jq empty on all schemas/*.json

Equivalent manual commands:

# Shell syntax check
find . -name '*.sh' -not -path './test-repos/*' | xargs bash -n

# Schema JSON validity
for f in schemas/*.json; do
    jq empty "$f" && echo "OK: $f" || echo "FAIL: $f"
done

Interpret failures

bash -n failure:

./lib/agent.sh: line 42: unexpected end of file

Means a syntax error at line 42 of lib/agent.sh. bash -n checks syntax only — it does not execute the script, so functions and variables are not evaluated.

jq empty failure:

jq: error: schemas/identity.json: Invalid numeric literal

Means schemas/identity.json is not valid JSON. Use python3 -m json.tool schemas/identity.json for a more informative error with line numbers.

Additional check: bundle.sh delimiter conflicts

If you changed any file in lib/, prompts/, scripts/, or added new files:

grep '__EOF_LIB_' lib/*.sh scripts/*.sh prompts/*.md 2>/dev/null

Any match means a file contains the exact heredoc delimiter used by bundle.sh, which will cause the bundle to self-truncate silently.

Verify

make check
echo "Exit code: $?"

Exit 0 = CI syntax job will pass. Then run make test-all for the full picture.

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.