yolo-verify

Étoiles9

Forks0

Mis à jour2 juillet 2026 à 17:28

Use to check a feature's work against its success_criteria and record the result. Produces verification.md and, on pass, the YOLO-Verified trailer. Triggers on "verify this", "does it meet the criteria", or as the verify step of yolo-feature.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

CoriChui

CoriChui/yolo

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	yolo-verify
description	Use to check a feature's work against its success_criteria and record the result. Produces verification.md and, on pass, the YOLO-Verified trailer. Triggers on "verify this", "does it meet the criteria", or as the verify step of yolo-feature.

yolo-verify

Decide, with evidence, whether the work satisfies the brief's success_criteria.

Inputs

workspace/features/<slug>/brief.md (success_criteria), the diff git diff <base_branch>...feature/<slug> (three-dot — only what the branch introduced; see .claude/yolo/conventions.md), and plan.md lint_commands/test_commands.

Procedure

Run the recorded lint_commands and test_commands. Capture pass/fail and key output.
For EACH criterion in success_criteria, gather concrete evidence (a passing test, an observed behavior, a code reference). Mark it met/unmet.
Write workspace/features/<slug>/verification.md: one section per criterion with its evidence, plus the lint/test results.

Outcome

All criteria met → commit the verification file with the trailer: git add workspace/features/<slug>/verification.md && git commit -m "yolo: verify <slug>" --trailer "YOLO-Verified: true"
Any criterion unmet → write the file recording what failed, do NOT write the trailer, and report the gap so execution can resume. A feature is never "done" without YOLO-Verified: true (.claude/yolo/conventions.md). The execute→verify loop is bounded (.claude/yolo/conventions.md The two gates); after repeated failure the caller should stop and escalate to the human rather than re-running, since that signals the plan or criteria need rethinking.

Constraints

The only file you write is verification.md. You do not edit code.
Verification is semantic (criteria), distinct from CI (mechanical) — yolo-finish handles CI.

Plus depuis ce dépôt

même dépôt

yolo-feature

CoriChui/yolo

Use when the user wants to build, add, or implement a feature. Captures intent, drafts a brief, confirms, then composes research → plan → execute → verify → finish. In a YOLO-initialized repo this takes precedence over generic brainstorming for feature intent.

2026-07-079

yolo-decide

CoriChui/yolo

Use when facing a design or architecture decision that benefits from multiple perspectives before committing. Produces a decision record under workspace/decisions/. Triggers on "help me decide X vs Y", "which approach", "should we use A or B".

2026-07-079

yolo-init

CoriChui/yolo

Use when setting up YOLO in a project for the first time, or repairing the setup. Scaffolds workspace/config.yaml and the features/, decisions/, and debug/ dirs (plus docs/ for the docs engine), and installs the CLAUDE.md routing block. Triggers on "set up YOLO here", "init yolo", "yolo init".

2026-07-079

yolo-intake

CoriChui/yolo

Use when a feature should draw on the project's reference material for context. yolo-intake does NOT fetch, import, or copy anything — it points YOLO at a selected folder (default `docs/`) and READS from it to enrich a feature's context. Getting material INTO that folder (a Figma, a spec, a URL, a schema) is the docs engine's or another connector's job, done separately. Triggers on "use the docs as context", "reference the spec/schema in docs", "the feature should read our docs".

2026-07-079

yolo-research

CoriChui/yolo

Use before planning a YOLO change, to understand the codebase and any cited intake before a plan is written. Read-only exploration that produces context for yolo-plan. Triggers on "understand how X works", "explore the code before we change it", or as the research step of yolo-feature.

2026-07-079

yolo-debug

CoriChui/yolo

Use when a reported problem, failure, or bug needs a systematic root-cause investigation — reproduce → isolate → fix → verify — recorded as one durable artifact. Triggers on "fix the 500 on login", "X is broken", "why is Y failing?", "debug this", "track down this bug".

2026-07-029

name	yolo-verify
description	Use to check a feature's work against its success_criteria and record the result. Produces verification.md and, on pass, the YOLO-Verified trailer. Triggers on "verify this", "does it meet the criteria", or as the verify step of yolo-feature.

yolo-verify

Decide, with evidence, whether the work satisfies the brief's success_criteria.

Inputs

workspace/features/<slug>/brief.md (success_criteria), the diff git diff <base_branch>...feature/<slug> (three-dot — only what the branch introduced; see .claude/yolo/conventions.md), and plan.md lint_commands/test_commands.

Procedure

Run the recorded lint_commands and test_commands. Capture pass/fail and key output.
For EACH criterion in success_criteria, gather concrete evidence (a passing test, an observed behavior, a code reference). Mark it met/unmet.
Write workspace/features/<slug>/verification.md: one section per criterion with its evidence, plus the lint/test results.

Outcome

All criteria met → commit the verification file with the trailer: git add workspace/features/<slug>/verification.md && git commit -m "yolo: verify <slug>" --trailer "YOLO-Verified: true"
Any criterion unmet → write the file recording what failed, do NOT write the trailer, and report the gap so execution can resume. A feature is never "done" without YOLO-Verified: true (.claude/yolo/conventions.md). The execute→verify loop is bounded (.claude/yolo/conventions.md The two gates); after repeated failure the caller should stop and escalate to the human rather than re-running, since that signals the plan or criteria need rethinking.

Constraints

The only file you write is verification.md. You do not edit code.
Verification is semantic (criteria), distinct from CI (mechanical) — yolo-finish handles CI.