agentleFS
Sign inStart free
kaeawckaeawc/auto-mobile/skills/shell-prepush/SKILL.md

shell-prepush

Skill56 starsChanged 34 days agoApache-2.0View on GitHub

Use this workflow skill before pushing shell or scripts changes to run scoped fast validation and targeted BATS tests, interpret stale dependency-pin failures, and retrieve empty Fast Validation logs from artifacts.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 are 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.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Use this before pushing changes under scripts/, shell hooks, agent skills, or related documentation.

    line 8
  2. Very specific:

    Run scripts/prepush-shell.sh.

    line 14
  3. Very specific:

    Run bun run format before pushing.

    line 17
  4. Very specific:

    If runtime-pins, sharp-matrix, or pin-runtime-deps.bats fails and bun.lock and/or package.json changed in the diff, run bun …

    line 19
  5. Very specific:

    Never run two bats test/bats/ sweeps concurrently on one machine.

    line 24
  6. Very specific:

    When an Actions API job log is empty, download the fast-validation-logs artifact and inspect its per-check .status and .log files under …

    line 26

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

Shell Prepush

Use this before pushing changes under scripts/, shell hooks, agent skills, or related documentation. It is a local pre-push check, not a replacement for the required CI jobs.

Workflow

  1. Run scripts/prepush-shell.sh; it compares the branch to origin/main, or main when the remote-tracking ref is unavailable, and selects only the applicable fast checks plus targeted BATS files.
  2. Run bun run format before pushing. Fast Validation runs bun run format:check as its first check and fails on drift.
  3. If runtime-pins, sharp-matrix, or pin-runtime-deps.bats fails and bun.lock and/or package.json changed in the diff, run bun scripts/release/pin-runtime-deps.ts --write and commit package.json, bun.lock, and scripts/release/runtime-graph.json; otherwise rebase onto current main and do not hand-edit pins to mask a stale base.
  4. Never run two bats test/bats/ sweeps concurrently on one machine. The targeted BATS invocation from prepush-shell.sh is safe to run on its own.
  5. When an Actions API job log is empty, download the fast-validation-logs artifact and inspect its per-check .status and .log files under scratch/fast-validate-*/.

Repo Validation Mapping

  • Shell/scripts pre-push: scripts/prepush-shell.sh
  • Scoped fast checks: ./scripts/all_fast_validate_checks.sh --only <names>
  • Targeted shell tests: bats test/bats/<matching-file>.bats
  • Formatting: bun run format

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