setup
/setup
Sprawdza i zapisuje ustawienia miejsca przechowywania artefaktów weryfikacji w repozytorium.
- Autor
- melodic-software ↗
- Repozytorium
- claude-code-plugins ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 26.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 4
- Skrypty
- 2
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/setup-apply.mjs, scripts/setup-apply.test.sh
Co robi i kiedy
Sprawdza i zapisuje ustawienia miejsca przechowywania artefaktów weryfikacji w repozytorium.
Wyzwalacze z opisu
Argumenty
/setup [check|apply] [proof_level=<path|live|strict>] [live_workers=<n>]
Oryginalny opis (EN)
Report where verification artifacts land and write the repository's docs/conventions/verification.yaml settings. check (read-only) names the memory root the verification skills resolve and validates the settings file; apply writes the keys its arguments name, proof_level, live_workers or both, after confirmation. Use when: 'set up verification', 'configure the verification plugin', 'is verification configured', 'verification setup', 'where do verification manifests / baselines land', 'set the proof level for this repo', 'set live workers for this repo'. Actions: check (read-only, default) | ap
Jak działa
- Purpose
- check (read-only)
- apply
- Output
- Next
- What this skill does NOT do
Podgląd SKILL.md
---
description: "Report where verification artifacts land and write the repository's docs/conventions/verification.yaml settings. check (read-only) names the memory root the verification skills resolve and validates the settings file; apply writes the keys its arguments name, proof_level, live_workers or both, after confirmation. Use when: 'set up verification', 'configure the verification plugin', 'is verification configured', 'verification setup', 'where do verification manifests / baselines land', 'set the proof level for this repo', 'set live workers for this repo'. Actions: check (read-only, default) | apply [proof_level=VALUE] [live_workers=N]. Re-runnable."
argument-hint: "[check|apply] [proof_level=<path|live|strict>] [live_workers=<n>]"
user-invocable: true
disable-model-invocation: true
---
## Purpose
Artifact placement is fixed by the plugin's lifecycle artifact protocol
([`${CLAUDE_PLUGIN_ROOT}/reference/artifact-protocol.md`](${CLAUDE_PLUGIN_ROOT}/reference/artifact-protocol.md)):
`/verification:confirm` writes its evidence manifest and `/verification:measure` its baselines and
raw captures into the memory slice `<memory_dir>/<slug>/`, never committed. `<memory_dir>` is `.work/`
unless the project's own instructions declare another root. Nothing about placement is configured.
The plugin owns one tracked settings file, `docs/conventions/verification.yaml`, the repository
layer of its settings, `proof_level` and `live_workers=<n>` (values, layers and the level rules:
[`${CLAUDE_PLUGIN_ROOT}/reference/config.md`](${CLAUDE_PLUGIN_ROOT}/reference/config.md); schema:
`${CLAUDE_PLUGIN_ROOT}/schemas/verification.schema.json`). `check` reports it; `apply` writes it
only when the operator names the key or asks to set the proof level. Idempotent: re-running reads
the current state again.
## `check` (read-only)
Report a PASS/INFO/WARN table. Do not write anything.
1. **Memory root.** Look for a working-docs root declared in the repo's own `CLAUDE.md`, `AGENTS.md`,
or `.claude/rules`. Report the declared root, or `.work/` when none is declared, as INFO.
2. **Ignore state.** Run `git check-ignore -v <memory_dir>/probe/baselines/x` on a representative
file path (a bare directory misses `**` patterns). A match is PASS and names the rule. No match is
INFO: the memory root's own self-ignoring `.gitignore` is created by the first memory-slice
write, announced, so an absent guard before any run is expected.
3. **Settings file.** Run `node "${CLAUDE_SKILL_DIR}/scripts/setup-apply.mjs" --check` from the
project root and add each line it prints with its own prefix: INFO when the file is absent
(`proof_level` and `live_workers` come from `userConfig` or their defaults), PASS with each
key's value when it validates, WARN when it does not (a `proof_level` outside `path`, `live`,
`strict`, a `live_workers` that is not a whole number of at least 1, a key set twice, an empty
value, null, a key the schema does not list, a file that does not parse, a list or map, a
symlink or hard link), quoting the file, key and value. A key the schema does not list is
ignored: the other keys keep their PASS lines, so a valid `proof_level` floor beside it counts.
A WARN never stops `/verification:confirm`: it names the value,
drops the layer and resolves that key's default (`path`, `1`). `apply` is the fix. `/verification:confirm` reads the default
branch's committed copy, so say that a working-tree value takes effect once it is merged there.
## `apply`
1. **Resolve the values.** Take each key the arguments name, `proof_level`, `live_workers` or
both, and use a complete `<key>=<value>` as given. For each named key without a value, ask once,
recommendation first:
- `proof_level`: `path`, the default, unless the team wants every runnable change driven live
(`live`) or per-phase unit, live and performance proof (`strict`). Before recommending `live`
or `strict`, say that a member on an older verification release does not read this file, so
the level only holds once every member has upgraded.
- `live_workers`: `1`, the default, unless the team wants the live drive split across workers
by feature-map entry point.
Never invent a key the schema does not list, and never adjust a value: the script decides
whether it is allowed.
2. **Write.** One call carrying every resolved key, each `<key>=<value>` as one quoted argument:
```bash
node "${CLAUDE_SKILL_DIR}/scripts/setup-apply.mjs" "proof_level=live"
node "${CLAUDE_SKILL_DIR}/scripts/setup-apply.mjs" "live_workers=3"
node "${CLAUDE_SKILL_DIR}/scripts/setup-apply.mjs" "proof_level=live" "live_workers=3"
```
The script checks each value against the schema (`live_workers` takes an unquoted whole number
of at least 1, so `0`, `1.5` and `'2'` are refused), refuses a key given twice, validates the
existing file, and validates the whole resulting document before it writes. In the existing file
it overwrites only a value outside the key's values, an empty value or null; it refuses a key set
twice, a map or list in block or flow form, an empty quoted string, an unknown key set twice or
holding a map or list, or a file that does not parse; any other unknown key is named in one
warning and its line kept as written. It writes only
`<git toplevel>/docs/conventions/verification.yaml`. It resolves a symlinked root first, then
refuses a root that is `$HOME` or an ancestor of it, a symlinked `docs`, `docs/conventions` or
target, a hard-linked target, or a `docs/conventions` that resolves outside the repository,
checked again before each directory it creates and right before the write. Every refusal is
one line, exits 1 and leaves the file as it
was; a failed write removes only its own temp file. A missing file is created; a value already
in place prints `already configured`.
3. **An existing file that would change** exits 3 and prints a unified diff without writing. Show
the operator that diff and ask whether to write it. Only on an explicit yes, re-run the same call
with `--yes`; on anything else, stop with the file unchanged.
4. **Verify.** Re-run the settings-file `check` row and report the value it prints, not the value
written. Then run `git check-ignore -v docs/conventions/verification.yaml` (a match is FAIL with
the pattern) and `git ls-files --error-unmatch docs/conventions/verification.yaml` (non-zero
right after a fresh write means "written but untracked: commit it to share with the team").
## Output
The `check` table. After `apply`: the diff shown, the written path, the value `check` reads back
for each key written, and whether the file is tracked.
## Next
`/verification:confirm`, which resolves `proof_level` from this file on the default branch.
## What this skill does NOT do
- Run a verification pass. That is the plugin's verification skills (`/verification:confirm`,
`/verification:measure`).
- Write any settings file other than `docs/conventions/verification.yaml`, edit any ignore file,
or write the plugin directory or the plugin data directory (`${CLAUDE_PLUGIN_DATA}` is for caches
and generated state only).
- Write Claude Code user settings or `pluginConfigs`. The per-user `proof_level` and
`live_workers` options are set through `/plugin configure`, not here.
Pliki w paczce (4)
- SKILL.md 7 KB
- evals/evals.json 6 KB
- scripts/setup-apply.mjs 1 KB
- scripts/setup-apply.test.sh 39 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · melodic-software/claude-code-plugins | 84 | MIT |
| HwangSlater/harness-fit | 100 | MIT |
| nesquikm/dev-process-toolkit | 100 | MIT |
| userKael/rastro | 100 | MIT |
| als-apg/osprey | 100 | BSD-3-Clause |
| dedujeong/gemba | 100 | Apache-2.0 |
| eigenwise/eigenwise-toolshed | 100 | MIT |
| awrshift/agent-memory-kit | 100 | MIT |
| lifecycle-innovations-limited/claude-ops | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 1847e7ef359a (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
- 95setup-deploy
Konfiguruje ustawienia wdrożenia dla /land-and-deploy: wykrywa platformę (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions), adres produkcyjny i health checki, a zapis trafia do CLAUDE.md. - 100setup-deploy
Konfiguruje wdrażanie dla /land-and-deploy: wykrywa platformę (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions), adres produkcyjny i health checki, a konfigurację zapisuje w CLAUDE.md. - 100repo-settings
Ujednolica ustawienia repozytorium GitHub: opis, metody scalania, reguły gałęzi, etykiety, Dependabot i profil społeczności. - 100okhp3-repository-settings
Audytuje i konfiguruje ustawienia repozytorium GitHub, w tym ochronę gałęzi, Actions, Pages, środowiska i przegląd Copilota, weryfikując każdy zapis. - 100gh-protect
Audytuje lub stosuje na GitHubie ochronę gałęzi, reguły tagów, ustawienia bezpieczeństwa repozytorium i wymagania podpisów zgodnie z aktywnym profilem. - 100video-setup
Przygotowuje projekt wideo pod resolve-video-skills: sprawdza narzędzia, ustawienia osi czasu i formaty oraz zapisuje zasady montażu.