deliver-direct-test

Implements approved code changes with scoped verification and regression evidence.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/skyrocoster/dnd-kids-resources --skill deliver-direct-test-skyrocoster
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deliver-direct-test
Source: https://github.com/skyrocoster/dnd-kids-resources/tree/main/.opencode/skills/deliver-direct-test
Command: npx skills add https://github.com/skyrocoster/dnd-kids-resources --skill deliver-direct-test-skyrocoster

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It enforces a disciplined delivery workflow for pre-approved code changes, ensuring edits stay within authorized paths, are backed by regression evidence, and pass required checks without unauthorized commits or scope creep. ## Core Features & Use Cases - Envelope Validation: Blocks execution unless the request includes explicit route approval, goal, authorized paths, known facts, a single change, a proof contract, closeout, and escalation conditions. - Scoped Implementation and Verification: Makes the smallest approved change, adds behavior-local regression guards, runs targeted pytest/Vitest, typecheck, and lint commands, then audits the git diff against authorized paths. - Controlled Closeout: Runs documentation checks, never commits, stops after two failed verification runs, and returns a structured result report (FIXED-PENDING-VALIDATION, VERIFIED, ESCALATED, or FAILED). - Use Case: A coordinator approves a one-line bug fix in a specific module; this Skill applies the fix, proves the regression red then green, runs the focused test suite, audits the diff, and reports results without touching anything else. ## Quick Start Resume the case-worker session with the approved change envelope and ask it to deliver the authorized fix with its proof contract.

Frequently Asked Questions about deliver-direct-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deliver an approved code change without expanding scope?▼

Provide the full approval envelope: route approval, goal, exact authorized paths, known facts, one change, a proof contract, closeout, and escalation conditions. The Skill makes only the smallest approved edit, audits the git diff against authorized paths, and escalates instead of widening scope.

What happens if required fields are missing from the approval?▼

Execution is blocked. The Skill requires explicit route approval, goal, authorized paths, known facts, a single change, a proof contract, closeout, and escalation conditions before any editing begins.

Does this workflow commit changes to git automatically?▼

No, it never commits. It preserves unrelated dirty worktree state, audits the diff, runs the required checks, and stops after reporting a structured result such as VERIFIED, ESCALATED, or FAILED.

Which tests and checks run during verification?▼

It runs every check named in the proof contract: targeted pytest or Vitest, typecheck for changed TypeScript contracts, lint for hook or dependency logic, and a documentation check script at closeout. Visible UI changes require a live check script.

When does the delivery workflow escalate instead of fixing?▼

It escalates when a fix requires unauthorized paths, would widen semantics or external contracts, is ambiguous, or exhausts the allowed verification attempts. It also stops after two failed verification runs total.