maintain-verification-skill
/maintain-verification-skill
Okresowo sprawdza skill weryfikacji aplikacji i mapę funkcji: równoległe czytanie kodu, jedna sesja na żywo i jeden zestaw poprawek.
- Autor
- TimothyVang ↗
- Repozytorium
- deepmodebot ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Okresowo sprawdza skill weryfikacji aplikacji i mapę funkcji: równoległe czytanie kodu, jedna sesja na żywo i jeden zestaw poprawek.
Wyzwalacze z opisu
Oryginalny opis (EN)
Periodic pass that keeps a project's verify-<app> skill and feature map honest: parallel read-only source readers per feature, one live session driving every feature, at most one change set of proven corrections. Use for /skill:maintain-verification-skill or \"audit the verify skill\".
Jak działa
- Outcomes
- Edit scope
- Pass
Podgląd SKILL.md
--- name: maintain-verification-skill description: "Periodic pass that keeps a project's verify-<app> skill and feature map honest: parallel read-only source readers per feature, one live session driving every feature, at most one change set of proven corrections. Use for /skill:maintain-verification-skill or \"audit the verify skill\"." disable-model-invocation: true --- # Maintain a verification skill A feature map rots the moment the app changes. This is the upkeep loop for a skill generated by `/skill:create-verification-skill` (or any project-local verification skill with a feature map). The unit of rigor is the feature, not every sentence: cover every feature file from source and exercise every feature live. ## Outcomes Pick one and say which: - **clean**: every feature got source and live coverage; nothing worth changing. - **changed**: one change set of proven doc, harness, or map corrections. - **blocked**: coverage could not finish, or a proven fix could not ship safely. Say exactly what blocked it. ## Edit scope Only edit the verification skill's own directory (its `SKILL.md`, `features/`, and harness scripts it owns). Never edit product code during a run. A behavior the map describes that the app no longer does is either doc drift (fix the map) or a product regression (report it; don't paper over it in docs). ## Pass 0. **Locate the target.** Glob `.omp/skills/verify-*/SKILL.md`, `.claude/skills/verify-*/SKILL.md`, and `.agents/skills/verify-*/SKILL.md` from the repo root (omp, Claude Code, and Codex and most other harnesses read those folders). Several candidates → pick the one whose app the change touches, and log why. None → stop and point at the **create-verification-skill** skill instead of inventing a target. 1. **Index hygiene.** Read `features/README.md` and glob its sibling files. Fix missing, extra, duplicate, or dead entries. 2. **Source wave.** One read-only `scout` task per feature file, in a single `task` batch. Each explains "how does this user-facing feature work?" from source, flags likely doc drift with file:line citations, and returns one concise live-verification recipe. Children never drive the app and never edit files. Return shape: feature summary / source entry points / likely drift or none / one recipe. 3. **Reconcile.** Every feature file has a returned summary. Merge overlapping recipes into as few app states as practical. Spot-check cited drift; don't re-prove clean claims. Sweep recent churn (`git log --since`) for user-facing surfaces missing from the map; require a concrete source path before calling one missing. 4. **Live pass.** Required even when source looks clean. You (the coordinator) own all driving. Follow the skill's own launch model: one long-lived instance driven serially for servers and UIs, or a fresh isolated session per drive for short-lived CLIs. Exercise every feature at least once. Hold three invariants whatever fails: - Never drive an instance you haven't doctored since it last did something surprising: doctor before the first drive, on each fresh session, and after any failed drive. Where doctor can't see the failure (a wedged UI on a healthy process), reset or relaunch rather than hoping. - Evidence captured so far survives every cleanup, checked at its named location, not assumed. - Nothing a drive started outlives its usefulness. For a shared instance, clean the residue, not the instance. A doctor failure caused by skill drift is drift: fix it under edit scope and retry once, restarting only what the fix invalidated, before calling the pass `blocked`. A feature is `verified-unreachable` only with the concrete prerequisite (auth, entitlement, OS, external state) and the route attempted; if the map omits that prerequisite, that's drift. Re-drive every harness fix live before it ships. Final teardown happens after the last drive, re-proofs included; evidence stays. 5. **Triage.** - Wrong or missing user-POV description → doc drift; fix it. - Working behavior the harness can't drive → harness gap; fix it (scripts executable, invocation documented in the skill body). - App behavior that's actually broken → product gap; record it for the user, keep it out of this change. 6. **Ship or stop.** For **changed**: re-read every changed file, then present one change set. Commit it and open a PR per deepmodebot's Opening a PR playbook (`skill://deepmodebot/references/playbooks/opening-a-pr.md`). For **clean** or **blocked**: no changes; report the outcome and coverage honestly. Keep run notes (features covered, unreachable prerequisites, confirmed drift, outcome) in a scratch location; don't commit them.
Pliki w paczce (2)
- LICENSE 1 KB
- SKILL.md 5 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · TimothyVang/deepmodebot | 100 | MIT |
| paperclipai/paperclip | 100 | MIT |
| Calvin-LLC/skills | 100 | MIT |
| arjitj2/open-pstack | 100 | MIT |
| chmonitor/chmonitor | 100 | GPL-3.0 |
| guangshinhaha/shinstack | 100 | MIT |
| backnotprop/pstack | 100 | MIT |
| chhoumann/t3-pstack | 100 | MIT |
| tommy-ca/pstack | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 27294d68b0ef (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
- 100checkup
Wykonuje okresowy przegląd, który utrzymuje w zgodności z rzeczywistością skill weryfikacji projektu i mapę funkcji: czytnik źródeł dla każdej funkcji, jedna sesja na żywo i najwyżej jeden PR z poprawkami. - 100prove-e2e-maintain
Sprawdza skill weryfikacji i mapę funkcji względem kodu, uruchamia każdą funkcję i proponuje poprawki w jednym pull requeście. - 86verify-maintain
Utrzymuje skill weryfikacji projektu i mapę funkcji w zgodzie z aplikacją po zmianach, nieudanych przebiegach lub audycie. - 100verification-skill
Tworzy i utrzymuje skill weryfikacji dla projektu, który uruchamia prawdziwą aplikację i zbiera dowody działania. - 100maintain-verification
Sprawdza, czy skill weryfikacyjny repozytorium i zestaw wzorców pasują do produktu: czyta kod, testuje funkcje na żywo i kończy stanem. - 86verify-create
Buduje własny skill weryfikacji projektu: uruchamia aplikację, przechodzi funkcje w przeglądarce i prowadzi mapę funkcji.