coder-xieshijie/dev-skills / skills/repo-readiness/assets/verify-skill
verify-<app>
FlaggedStarts isolated <app> instances, drives them through <entry points> and reports one result per sub-feature and entry with evidence. Use when verifying a change, reproducing a bug, or running, writing or checking feature maps and their scenario scripts.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.7 KB |
| features/README.md | markdown | 1.4 KB |
| references/maps.md | markdown | 11.4 KB |
| scripts/config.mjs | script | 5.2 KB |
| scripts/contract.mjs | script | 16.6 KB |
| scripts/map-check.mjs | script | 22.2 KB |
| scripts/primitives.mjs | script | 7.2 KB |
| scripts/runner.mjs | script | 24.0 KB |
| scripts/test/contract-check.test.mjs | script | 3.7 KB |
| scripts/test/contract.test.mjs | script | 1.4 KB |
| scripts/test/fixture/notes-entry.mjs | script | 3.5 KB |
| scripts/test/fixture/proc-app.mjs | script | 1.3 KB |
| scripts/test/fixture/proc-entry.mjs | script | 5.5 KB |
| scripts/test/fixture/web-entry.mjs | script | 535 B |
| scripts/test/helpers.mjs | script | 5.0 KB |
| scripts/test/map-check.test.mjs | script | 9.5 KB |
| scripts/test/primitives.test.mjs | script | 4.1 KB |
| scripts/test/runner.test.mjs | script | 17.3 KB |
| scripts/verify.mjs | script | 9.7 KB |
| verify.config.json | config | 1016 B |
features/README.md
View on GitHub# Feature maps
Each map is the only spec of one feature's sub-feature behavior: what the sub-features are, how a user reaches each at every entry point, what to do, and the numbered criteria that decide the result. Results are not kept here; they stay in each run's evidence directory.
Pick the maps a change touches, run their scenario scripts (`node $V run <map>`), drive the entries that have no scripts by hand, and report one result per sub-feature × entry. Writing or changing a map: [references/maps.md](../references/maps.md).
Every map is scripted at the entries in `verify.config.json` `scripted` (<list them, or "none yet">); the Also scripted column adds entries for one map. `node $V check` prints each map's scripted entries. The Spec column links a spec with requirement ID headings, or names the docs and source files that define the behavior as code spans when there are no IDs.
<!-- Links are relative to this file: from <skills dir>/verify-<app>/features/ the repository root is four levels up when <skills dir> is two directories deep (.agents/skills, .claude/skills). -->
| Feature | Map | Spec | Also scripted | Content |
|---|---|---|---|---|
| <Feature> | [<map>.md](../../../../<map root>/<feature>/feature-map/<map>.md) | [spec.md](../../../../<map root>/<feature>/spec.md) or `<path/to/design.md>` | <entries scripted for this map only, comma-separated> | <one-line scope> |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |