agentleFS
developerz-aideveloperz-ai/gold-standards-in-ai/.claude/skills/verify-change/SKILL.md

verify-change

Skill2 starsChanged yesterdayMITView on GitHub

Prove a change in developerz-ai/gold-standards-in-ai before committing or opening a pull request — the repo's own install, run and check commands. Use before every commit.

24 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Run every command from the repo root — the scripts cd there themselves.

    line 24
  2. Distinctive:

    Add the test that fails first, then the fix — a green run that never went red proves nothing.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “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

Verify a change in developerz-ai/gold-standards-in-ai

House skill — owned by this repository's maintainers from this repo’s own detected commands. Correct it in place; setup never overwrites a skill that exists.

The one gate

bin/check is the gate. CI runs it and the pre-commit hook runs it, so a change that passes it locally passes everywhere.

StepCommandWhat it is
installbin/setupecho "gold-standards-in-ai: markdown only, no dependencies to install"
runbin/devecho "gold-standards-in-ai: no app to run - read README.md for the map" — on developerz.ai runs, start it with code_bash_background when you need a running stack
provebin/checkruns bin/check-docs (index + relative-link + #fragment validation) then bin/test (its regression fixtures); silent on success. Exits 0 when the change passes, 75 when a gate precondition is unmet, any other nonzero for a validation or regression failure. The real gate is bin/check-docs — run it, never copy its slug rules
stopbin/stoptrue — on developerz.ai runs, the platform runs this when your session ends — do not stop the stack yourself

Rules

  • Run every command from the repo root — the scripts cd there themselves.
  • bin/check red is not a pull request. Fix the cause, never silence the gate.
  • The gate's rules live in bin/check-docs; read them there instead of copying them:
    • a doc under docs/ needs the root README.md and its section README.md to carry it;
    • a #fragment is the slug of the target's heading — lowercase, every character that is not a letter, a digit, - or _ deleted, spaces turned into -. ## ⌨️ Keyboard paths is -keyboard-paths; ## 6. Merge → deploy without a human bottleneck is 6-merge--deploy-without-a-human-bottleneck.

Exit codes bin/check uses

A coding box runs this gate before it commits, and it has to tell a FAILING change from a gate it could not run — otherwise correct work is thrown away as if it were red. Exit 1 cannot carry that difference, so one code is reserved:

ExitMeansWhat the platform does
0the change passescommit it
75a gate precondition is unmet — the gate could not graderefuse the commit, and blame the environment, never the change
any other non-zerovalidation or regression failed — the gate ran and the change is redrefuse the commit, and blame the change
  • Guard preconditions FIRST and exit 75 when one is unmet. exit 1 there tells the platform your change is broken when it is your environment that is.
  • Changed a dependency? Re-run bin/setup before bin/check, or you are proving a stale tree.
  • Add the test that fails first, then the fix — a green run that never went red proves nothing.

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.