create-verification

Scaffolds a repository-local verification contract, feature maps, and a mise verify task from observed checks.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/douglasjarquin/sum --skill create-verification-douglasjarquin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-verification
Source: https://github.com/douglasjarquin/sum/tree/main/.agents/skills/create-verification
Command: npx skills add https://github.com/douglasjarquin/sum --skill create-verification-douglasjarquin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Repositories often lack a documented, executable verification standard, so agents and contributors cannot prove their changes work. This Skill inspects a repository and generates a complete project-local verification setup that is proven by running it once. ## Core Features & Use Cases - Repository Inspection: Reports guidance files, mise tasks, package scripts, make targets, HTTP routes, CLI entrypoints, test locations, and installed driver capabilities without writing anything. - Verification Scaffolding: Generates VERIFY.md, a verify mise task composed from existing checks, seed feature maps under docs/features/, and vendored verify/maintain-verification skills, never overwriting existing files. - Proof Run and Audit: Drives one mapped feature end to end with evidence capture, then audits the maps until no TODO(verify) placeholders remain. - Use Case: Point it at a freshly cloned web service; it detects the test task and health endpoint, writes the contract and feature maps, runs the verification once, and hands off a maintenance loop. ## Quick Start Ask the agent to inspect this repository and bootstrap its verification contract, feature maps, and verify task, then prove them with one real run.

Frequently Asked Questions about create-verification

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

FAQPage Schema
How do I add a verification contract to an existing repository?

Run the scaffold script in inspect mode first to see what the repository declares, then run it with --write to generate VERIFY.md, a verify mise task, and seed feature maps. Fill the TODO(verify) placeholders from observation and prove the setup with one real run.

How does the verify task get created from existing checks?

The scaffold composes the verify task from check tasks the repository already declares, such as mise test/lint/check tasks, npm scripts, make targets, or a discovered Python test directory. If nothing reusable exists, it writes no task and reports the problem instead of faking success.

Does create-verification require sum or Herdr to run?

No, the skill is portable and works in any Git clone with mise and Python 3.11 or newer. No sum installation, Herdr session, .sum directory, or absolute path outside the target repository is involved.

Will the scaffold overwrite my existing VERIFY.md or feature maps?

No, generation is idempotent and never overwrites. Existing files without placeholders are kept, conflicting drafts are preserved with the proposal written under .artifacts/verification/scaffold/, and re-running on a completed repository writes nothing.

What happens when no browser or HTTP driver is installed?

The scaffold only names drivers whose capabilities are actually installed, such as curl, playwright, or chrome-devtools-axi. A surface without an installed driver is marked explicitly manual in the feature map rather than given an invented recipe.