legion-verify

Validates issue acceptance criteria against diffs and test output with cited evidence verdicts.

3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/runlegion/legion --skill legion-verify-runlegion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legion-verify
Source: https://github.com/runlegion/legion/tree/main/plugin/skills/legion-verify
Command: npx skills add https://github.com/runlegion/legion --skill legion-verify-runlegion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finished work often gets closed without proof it actually meets the issue's acceptance criteria. This Skill acts as the final QA gate: it reads each criterion, gathers evidence from the diff and test runs, and records a pass, fail, or uncertain verdict per criterion before an issue can be closed. ## Core Features & Use Cases - Criterion-by-criterion verdicts: Loads acceptance criteria via legion issue view and emits exactly one verdict per criterion, each backed by a test name, file:line, or observed behavior. - Vacuous evidence rejection: Automatically demotes passes whose evidence merely restates the criterion or describes implementation without an assertion marker. - Close-gate enforcement: legion verify --issue records the verdict; any fail or uncertain blocks legion issue close, while all-pass unblocks it. - Use Case: After finishing an auth refactor, run the verify gate against issue #42 to confirm each acceptance criterion is proven by a real test before closing the issue. ## Quick Start Ask the agent to verify issue 42 in the myapp repo by checking each acceptance criterion against the diff and test results, then recording the verdicts with legion verify.

Frequently Asked Questions about legion-verify

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

FAQPage Schema
How do I verify acceptance criteria before closing an issue?

Load the criteria with legion issue view, gather evidence from git diff and test runs, write one verdict per criterion to a JSON file, then record it with legion verify --repo <repo> --issue <n> --verdicts-file. All-pass unblocks closure; fail or uncertain keeps it blocked.

What counts as valid evidence for a pass verdict?

Valid evidence cites a test name, a file:line reference, or an observed behavior that confirms the criterion. Restating the criterion or describing implementation details without an assertion marker is treated as vacuous and demoted to uncertain.

What happens when a criterion cannot be mechanically confirmed?

Mark it uncertain rather than rounding up to pass. The verify command exits non-zero, issue closure stays blocked, and a human adjudicates the criterion, which is the intended behavior of the gate.

Why does legion issue close refuse to close my issue?

Issues with acceptance criteria cannot close until legion verify records a clean all-pass verdict. Any fail, any uncertain, or missing criteria on the issue keeps the close gate blocked.

What is the difference between legion verify and vault review?

Verify owns acceptance: whether the work meets the stated criteria with evidence. Vault owns intent: whether the right work was done and the spec is serviced. They are separate gates and should not be conflated.