void-verify

Runs a twelve-item observed pre-flight checklist before reporting any task as done.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-verify-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-verify
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/core/skills/void-verify
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-verify-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completion claims often rest on belief rather than observation: tests "passed earlier," lint "should be clean," the mobile view "is probably fine." This Skill replaces assumptions with a final pre-flight checklist where every item is actually observed before work is reported as done. ## Core Features & Use Cases - Twelve-Item Verification Checklist: Covers typecheck, tests, lint, coverage, hooks, mobile and desktop viewports, observability, security review, documentation, commit message rationale, review evidence, and plan linkage. - Plan Completion Audit: Classifies every actionable plan item as DONE, PARTIAL, NOT DONE, CHANGED, or UNVERIFIABLE, with per-item confirmation for anything unverifiable and explicit naming of scope creep. - Explicit Skip Discipline: Items may be skipped only with a stated reason in the completion report; silent skipping is treated as a defect. - Use Case: After finishing a bug fix or a plan step, run the checklist to produce a completion report showing each item as observed or skipped with a reason, so reviewers see real signals instead of assurances. ## Quick Start Ask the agent to run the final verification checklist and report each item as observed or skipped with a reason before marking the task done.

Frequently Asked Questions about void-verify

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

FAQPage Schema
How do I verify a coding task is actually complete before reporting done?

Run the twelve-item pre-flight checklist at the end of the task. Each item, such as typecheck, tests, lint, and hooks, must be observed by re-running the command rather than assumed from earlier results, and any skipped item needs an explicit stated reason.

What is a plan completion audit in code review?

It classifies every actionable item from a plan or ticket against the actual diff as DONE, PARTIAL, NOT DONE, CHANGED, or UNVERIFIABLE. Code that merely handles a deliverable does not count as the deliverable, and each unverifiable item is confirmed individually.

Can I skip checklist items for small changes?

Items can be skipped only with an explicit stated reason in the completion report, such as no UI change for the viewport item. Silent skipping is treated as the defect this checklist exists to prevent, and small changes are where the discipline pays most.

Does this verification checklist work with TDD and code review workflows?

Yes, it composes with TDD skills for test and coverage items, feeds the review evidence block for pull requests, and updates the plan resume point for multi-step plans. It runs last, after every other skill in the workflow.

Why did my completion report get rejected as not observed?

Statements like "tests should pass" or "lint was fine earlier" are assumptions, not observations. If code changed since the last run, the previous result is stale; re-run the command and cite the fresh output.