vstack-s8-package-maintain — Claude Code skill: regression
The vstack-s8-package-maintain Claude Code skill turns verified project scope into a five-step regression workflow. It handles regression setup and upkeep as code changes.
MIT ★ 89 updated 2026-11-16
/plugin marketplace add hao-ai-lab/vstack
/plugin install vstack@hao-ai-lab-vstackWhat vstack-s8-package-maintain does
The skill turns accepted outputs from stages S4–S7 into a project-local regression check and keeps it aligned with later code revisions. Its verification template records coverage, the synced revision, assumptions, bounds, a command, expected results, and triage rules.
Checks run in sequence: pins, drift, model, trace regression, then mutation regression. The skill also requires breaking protected logic in a source copy, recording the result, and checking that restoration returns the baseline to green. After upstream changes, it runs the existing check first and classifies changes to covered state.
Deductive claims require retained proof trees, tool and settings hashes, raw logs, and acceptance evidence. The five-step regression cannot renew a proof claim on its own. A blocked run leaves the synchronized revision unchanged.
What it helps with
- package accepted artifacts as a repeatable regression check
- detect model drift after upstream code changes
- test whether protected logic changes make a check fail
- separate model updates from product fixes
- retain evidence for deductive claims
Example prompts for the agent
- Package the accepted S4–S7 outputs as a regression skill with ordered checks.
- Test whether the regression catches a break in protected logic and passes after restoration.
- Update the checks after code changes and classify affected state.
How to install vstack-s8-package-maintain
1Plugin marketplace
/plugin marketplace add hao-ai-lab/vstack/plugin install vstack@hao-ai-lab-vstackThis installs the whole vstack plugin with all its skills
2Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-s8-package-maintain -a claude-code3Manually: put the files in place
~/.claude/skills/vstack-s8-package-maintain/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vstack-s8-package-maintain/
1Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-s8-package-maintain -a codex2Manually: put the files in place
.agents/skills/vstack-s8-package-maintain/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-s8-package-maintain -a cursor2Manually: put the files in place
.cursor/skills/vstack-s8-package-maintain/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install hao-ai-lab/vstack skills/vstack-s8-package-maintain2Manually: put the files in place
.github/skills/vstack-s8-package-maintain/SKILL.md1Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-s8-package-maintain -a gemini-cli2Platform CLI
gemini skills install https://github.com/hao-ai-lab/vstack --path skills/vstack-s8-package-maintainManually: put the files in place
.devin/skills/vstack-s8-package-maintain/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about vstack-s8-package-maintain
How do I install vstack-s8-package-maintain in Claude Code?
Add the marketplace with /plugin marketplace add hao-ai-lab/vstack, then install the plugin with /plugin install vstack@hao-ai-lab-vstack.
What does vstack-s8-package-maintain do?
It packages verified scope as a project-local, five-step regression workflow and maintains it as code changes. For deductive claims, it preserves evidence and handles proof-gate requirements separately.
How does the skill test changes to protected logic?
It calls for a break in a source copy and records whether the check fails. After the logic is restored, the baseline check should pass.
Source text
SKILL.md · MIT
--- name: vstack-s8-package-maintain description: "Package verified scope into a project-local five-step regression skill and keep it aligned with future code revisions." --- # S8 — Package and maintain regression Read [Layer 0: shared operating rules](../../docs/layer-0.md), this stage and the assigned input bundle. ## Role and write scope One author per case skill; the coordinator owns gold and independently reviews evidence. Only the coordinator integrates changes. ## 1. Input The accepted artifacts from S4, S5, S6 and S7, as required by the S1 route: models, configurations, traces, mutations, expectations and hashes. ## 2. Procedure 1. Fill [verify-skill](../../templates/verify-skill.md): coverage, synchronized revision, assumptions, bounds, one command, expected results, triage rules and the full [adequacy readout](../../docs/model-adequacy.md) of the model at that revision. 2. Run five checks in order: pins, drift, model, trace regression, then mutation regression. Keep the regression small and repeatable; measure and report its duration. 3. Break protected logic in a source copy: the check must turn red. Restore it: green with the baseline. Record prediction versus actual, including failed predictions. 4. After upstream changes, run unchanged first. Inspect all changes to covered state, including moved or new writers. Classify each as no effect, model drift, intentional promise change or possible code bug. 5. Update models from source, not from desired verdicts. Recalibrate after alignment changes and update the sync revision only after alignment succeeds. Keep verification and product-fix changes distinct. 6. For deductive claims, retain the frozen proof tree, tool and settings hashes, raw logs and [full acceptance evidence](../../docs/gates.md#deductive-proof-acceptance). Publish the root statement and premises verbatim. Bind every module result, including slice certificates, to its source, full import closure and toolchain. Refresh changed closures through the root; proof-body-only changes permit unchanged downstream reruns with persistent fingerprints, while definition or invariant changes require contract review and renewed acceptance. The five-step regression cannot renew a proof claim alone. ## 3. Exit checks - Record both break and restore results. Require the independent clean regression rerun to match every expected row. Review deductive evidence under the proof gates without imposing a second same-source proof run. - Distinguish baseline reproduction from a required-fix check and explain stale frozen trace evidence. - Report maintenance as in sync, updated, bug or blocked. A blocked run does not advance the synchronized revision. - Identify the proved design model in deductive claims; describe the implementation as validated against it. An independent reviewer must complete the proof gates before a machine-proof claim. ## 4. Rollback Return model drift to S3, then rerun S4. Send intentional promise changes to S2 and code violations to S6. Report BLOCKED if tools or alignment are unavailable; do not move the sync commit. Use [a rollback ticket](../../templates/rollback.md). ## Concrete Examples The [PD example](../../examples/verify-pd-kv-slot/SKILL.md) describes pins, drift, model checks, trace checks and mutations. Frozen trace checks can stay unchanged after a live source mutation; drift and source-derived model variants must detect that change.
© Hao AI Lab · MIT · hao-ai-lab/vstack