Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

verify-setup

/verify-setup

Tworzy w repozytorium zestaw weryfikacyjny w katalogu .agents/verify: diagnostykę, kontrole i sterowniki funkcji.

Repozytorium
skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
16.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
16
Skrypty
10
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 16.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 10 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: assets/verify/check.sh, assets/verify/doctor.sh, assets/verify/drive/example.sh, assets/verify/fresh.sh, assets/verify/lib.sh, assets/verify/observe.sh, scripts/scaffold.mjs, scripts/test-fresh.sh, scripts/test-observe.sh, scripts/test-scaffold-check.sh

Co robi i kiedy

Tworzy w repozytorium zestaw weryfikacyjny w katalogu .agents/verify: diagnostykę, kontrole i sterowniki funkcji.

Oryginalny opis (EN)

Give a repository its own executable verification kit under .agents/verify: doctor, deterministic checks, per-feature drivers that observe the real surface and keep evidence tied to the exact tree, and an enforcer table. Use when a repo has no way for an agent to prove a change works, when setting up verification for a new repo, when adding a driver for a feature, when a done claim was wrong because the wrong surface was checked, or when the verify-before-done hook blocks for lack of evidence. Do not use to review a diff (gate) or to record a case (correct).

Jak działa

  1. Kit
  2. Procedure
  3. Rules
  4. Maintenance
Sekcje z nagłówków SKILL.md, w oryginale · 47 linii, 708 słów
Podgląd SKILL.md
---
name: verify-setup
description: "Give a repository its own executable verification kit under .agents/verify: doctor, deterministic checks, per-feature drivers that observe the real surface and keep evidence tied to the exact tree, and an enforcer table. Use when a repo has no way for an agent to prove a change works, when setting up verification for a new repo, when adding a driver for a feature, when a done claim was wrong because the wrong surface was checked, or when the verify-before-done hook blocks for lack of evidence. Do not use to review a diff (gate) or to record a case (correct)."
compatibility: "Requires git, bash, and Node or Bun for the scaffold. Drivers use whatever the surface needs, such as agent-browser, curl, or the repo's own CLI."
---

# Verify setup

A repo is verifiable when an agent that has never seen it can run one command and get evidence, from the surface a user touches, that a change works. Prose that says how to check is not enough. This skill ships scripts.

## Kit

`node scripts/scaffold.mjs <repo-root> [--local]` copies the kit into `<repo>/.agents/verify/` and never overwrites. `--local` adds `.agents/verify/` to `.git/info/exclude`, so the kit works on this machine without ever being versioned. Use it for repos you do not own:

| File | Contract |
|---|---|
| `doctor.sh` | exit 0 only when every precondition the drivers need exists |
| `check.sh` | types, lint, unit tests; non-zero on any failure |
| `observe.sh <feature> [--runs N]` | runs `drive/<feature>.sh` with `EVIDENCE_DIR` set, N times when asked; passes only if every run passes; `meta.json` records tree digest, exit, runs, passed. `observe.sh check` runs `check.sh` |
| `fresh.sh` | exit 0 when every contract feature passed on its latest observation of the current tree contents; `observe: f x5` also needs at least 5 runs; the Stop hook calls it |
| `lib.sh` `artifact_current <artifact> <src>...` | fails when a built artifact is older than its sources, so a driver never observes another build |
| `drive/<feature>.sh` | reaches the feature as a user does and writes proof into `EVIDENCE_DIR` |
| `features/<feature>.md` | where it lives, how a user reaches it, how to drive it, what usually lies |
| `ENFORCERS.md` | rule to enforcer table |

`evidence/` is gitignored. The tree digest covers tracked changes and untracked files, so evidence from before an edit never counts after it.

## Procedure

1. Read the repo's README, CI config, and agent instructions. List the surfaces: CLI, HTTP API, web UI, desktop, library.
2. Scaffold the kit. Fill `doctor.sh` with the real binaries, env vars and services. Fill `check.sh` with the commands CI runs, fastest first.
3. Pick the three to five features changes touch most often (git log, open issues). For each, write the driver and the feature file.
4. A driver observes the outcome, not a proxy. When it loads a built artifact (binary, WASM, bundle), it first proves the artifact came from this tree: `artifact_current`, or rebuild and compare with the committed copy. A benchmark driver measures the baseline in the same run (origin/main and this tree, same browser) and is declared with `x<N>` in the contract, since one run of a noisy number is a coin flip. A CLI driver runs the built binary and asserts on output. A web driver uses agent-browser to screenshot and asserts on the DOM or text. An API driver curls the running service and asserts on the body, not only the status.
5. Fill "What usually lies" from real failures: cases in the canonical repo under `cases/<repo>/`, review findings, and papercuts.
6. Prove the kit before handing it over: `doctor.sh`, `check.sh`, then `observe.sh <feature>` for every driver, on a clean tree. Open each screenshot and look at it. Then break the feature on purpose (or revert a known fix) and confirm the driver fails. A driver that cannot fail is not a driver.
7. Report the commands run, exit codes, and evidence paths.

## Rules

- Never mark a driver done because it exited 0. It is done when it has been seen to fail on a broken state and pass on a fixed one.
- Drivers are deterministic and idempotent. They clean up what they start, also on failure.
- Do not mock the surface. If the real surface needs credentials or a service that is unavailable, `doctor.sh` fails with that reason; never fall back to a fake.
- Label each claim in reports as measured, inferred, or guess.
- In a repo you do not own, scaffold with `--local`. Proposing the kit upstream is a human decision.

## Maintenance

Run `node scripts/scaffold.mjs <repo-root> --check` before relying on a kit: it fails when `lib.sh`, `observe.sh`, or `fresh.sh` differ from this skill's copies. Copy the current ones over; repo-specific files are left alone.


When a change adds or moves a feature, update its driver and feature file in the same diff. When a mistake escapes, add a check that fails on that mistake and a row in `ENFORCERS.md`.
Pliki w paczce (16)
  • SKILL.md 5 KB
  • assets/verify/.gitignore 1 KB
  • assets/verify/ENFORCERS.md 1 KB
  • assets/verify/check.sh 1 KB
  • assets/verify/doctor.sh 1 KB
  • assets/verify/fresh.sh 2 KB
  • assets/verify/lib.sh 1 KB
  • assets/verify/observe.sh 2 KB
  • assets/verify/drive/example.sh 1 KB
  • assets/verify/features/README.md 1 KB
  • evals/evals.json 2 KB
  • evals/triggers.json 1 KB
  • scripts/scaffold.mjs 2 KB
  • scripts/test-fresh.sh 2 KB
  • scripts/test-observe.sh 3 KB
  • scripts/test-scaffold-check.sh 1 KB

Wersje

W bazie nie ma innych skilli o nazwie verify-setup.

Migawka bazy z 13.11.2026 · wersja paczki dbc03104c5b9 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100setup
    Konfiguruje zestaw weryfikacyjny Rung w repozytorium: lintery, testy i skany jako sprawdzenia oraz bramkę w CI dla pull requestów.
  • 95rung-setup
    Konfiguruje w repozytorium zestaw weryfikacyjny Rung: rejestruje testy, lintery i skany bezpieczeństwa, uruchamia je i raportuje wyniki.
  • 100create-verification-skill
    Generuje lokalny skill weryfikacji z CLI sterującym aplikacją, mapą funkcji i dowodami, tak jak zrobiłby to użytkownik.
  • 86verify-create
    Buduje własny skill weryfikacji projektu: uruchamia aplikację, przechodzi funkcje w przeglądarce i prowadzi mapę funkcji.
  • 100verify-changes
    Zestaw weryfikacyjny dla agent-hq: dobiera minimalny zestaw faz do kształtu zmiany przed zapisem lub scaleniem.
  • 100setup-kit
    Ustawia pliki AGENTS.md, strażników agentów, kontrole lint i CI oraz ustawienia repozytorium w dowolnym języku.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.