Runs a repository's VERIFY.md verification contract and records candidate-bound evidence.
npx skills add https://github.com/douglasjarquin/sum --skill verify-douglasjarquin
Please help me install this Agent Skill. Skill: verify Source: https://github.com/douglasjarquin/sum/tree/main/.agents/skills/verify Command: npx skills add https://github.com/douglasjarquin/sum --skill verify-douglasjarquin
mise run verify task belongs to this repository, and runs it with a timeout. - Evidence capture: Records per-feature command and HTTP evidence (exact command, output, expectations met) into a run directory that teardown never deletes. - Truthful outcome reporting: Distinguishes pass, fail, blocked, not-run, and not-applicable; flags dirty trees as provisional and policy-file changes as requiring root review, so a candidate cannot certify itself. - Use Case: After fixing a bug on a branch, run the verify skill to execute the project's checks, capture evidence for the affected feature, and produce a run record a reviewer can inspect before merging. ## Quick Start Ask the agent to verify this repository by running the verify skill, which reads VERIFY.md at the project root and executes the canonical mise run verify task while recording the results.High-intent search queries and answers about installing and using this skill.
Run verify_run.py from the skill's scripts directory at the project root. It reads VERIFY.md, validates the contract and feature maps, confirms the mise verify task belongs to this repository, runs `mise run verify`, and writes a run record under the artifacts directory.
Use verify_capture.py with the feature ID and either a run recipe (a command with expected exit code or output text) or an http recipe (a request with expected status or body text). Each capture writes a JSON evidence file into the run directory's evidence folder.
Yes, the skill is fully portable and works in any ordinary clone. It only requires Git, mise, and Python 3.11 or newer; everything it needs lives inside the repository being verified.
Blocked means the run could not be trusted: VERIFY.md is missing or malformed, the verify task is missing or inherited from a parent project, a required command is absent, or the run timed out. Blocked is never reported as a pass.
A run requires root review when policy files such as VERIFY.md, mise tasks, or feature maps changed relative to the --base ref, or when no base was provided. Such a run cannot certify a commit SHA, since a candidate must not modify the rules that judge it.
No. A dirty tree produces a provisional record that is not bound to an exact commit SHA. Commit your changes first when you need a result that certifies a specific SHA.
filipstrandDiscover and summarize MFLUX CLI commands and capabilities.
dangvu008Classifies, verifies, and implements code review feedback with pushback and rejection tracking.
spencerpaulyCapture before-and-after screenshots of UI changes for pull requests.
jmaglyAnalyze CI history and test execution patterns to identify flaky tests.