Skip to content
Back to skills

Verify Change

ASecurity

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.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 9, 2026
ai-agentsgobashgit

Security analysis

A100/100

Scanned November 9, 2026

npx -y skills add developerz-ai/gold-standards-in-ai --skill verify-change --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Verify Change?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Verify Change
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/developerz-ai-verify-change-gold-standards-in-ai/badge)](https://www.skillsdirectory.com/skills/developerz-ai-verify-change-gold-standards-in-ai)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: 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.
---

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

> House skill — established by dz-runner setup mode 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.

| Step | Command | What it is |
|------|---------|------------|
| install | `bin/setup` | echo "gold-standards-in-ai: markdown only, no dependencies to install" |
| run | `bin/dev` | echo "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 |
| prove | `bin/check` | runs `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 |
| stop | `bin/stop` | true — 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:

| Exit | Means | What the platform does |
|------|-------|------------------------|
| 0 | the change passes | commit it |
| 75 | a gate precondition is unmet — the gate could not grade | refuse the commit, and blame the environment, never the change |
| any other non-zero | validation or regression failed — the gate ran and the change is red | refuse 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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.