verify

Original：🇺🇸 English

Translated

1 scriptsChecked / no sensitive code detected

The one definition of what each gate runs. Use to run a gate stage, to add or change a check, or to read why a step exists.

10installs

Sourcetimschoch/skilly

Added on2026-09-25

NPX Install

npx skill4agent add timschoch/skilly verify

SKILL.md Content

View Translation Comparison →

Verify

.skilly/verify.json

says what each gate runs. Hooks and CI call a stage of it, so the local gate and the pipeline cannot drift into disagreeing about what green means.

Usage

sh

node .agents/skills/verify/scripts/verify.mjs <stage>           # run the stage
node .agents/skills/verify/scripts/verify.mjs <stage> --steps   # resolved steps as JSON, runs nothing

Works from anywhere in the Consumer. Exit 0 passed, 2 config or usage error, anything else is the failing step's code.

Config

json

{
  "budgetTicket": "https://github.com/owner/repo/issues/1",
  "stages": {
    "commit": { "budgetSeconds": 10, "steps": [{ "name": "lint-staged", "run": "npx lint-staged", "why": "the reason this step exists" }] },
    "push": { "extends": "commit", "budgetSeconds": 120, "steps": [] },
    "ci": { "extends": "push", "budgetSeconds": 600, "steps": [] },
    "nightly": { "tier": "product", "budgetSeconds": 1800, "steps": [{ "name": "e2e", "run": "npm run e2e", "target": "e2e" }] }
  }
}

extends

is cumulative:

push

runs every

commit

step first, so no stage can skip a check the stage below it runs.

A budget warns and never fails. A gate that fails on slowness teaches you to bypass the gate, and the bypass outlives the slowness.

budgetTicket

says where a stage that outgrew its budget gets split.

Tier

tier

in

.skilly/config.json

, default

sandbox

, order

sandbox

<

tool

<

product

. A step's

tier

is the minimum a repo needs to run it; below that the step is skipped. A stage's

tier

is that rule for the whole stage: below it nothing runs and the exit is 0. Tier sets the size of the net, not the standard.

Target

A step's

target

is a path relative to the repo root; missing, the step is skipped. That is how one stage list fits repos that do not all have an

e2e/

or a Dockerfile.

Adding a check

One step in

.skilly/verify.json

, never a line in a hook or a workflow. Give it a

why

: it prints the moment the step goes red, when the reader is least likely to go looking for it.