Skill
yolo-debug
Use when a reported problem, failure, or bug needs a systematic root-cause investigation — reproduce → isolate → fix → verify — recorded as one durable…
Development
Skill
/yolo-research
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
Install
$ npx -y skills add CoriChui/yolo --skill yolo-research --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/yolo-research
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
yolo-research.SKILL.mdname: yolo-research
description: 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.
yolo-research
Read-only exploration. You gather the context a plan needs; you change nothing.
Inputs
- A brief (`workspace/features/<slug>/brief.md`) — read `goal`, `success_criteria`, `intake_refs`.
Or, when invoked standalone, a plain question.
Procedure
1. Identify the relevant surface: `Glob`/`Grep` for the entities, modules, and routes named in the goal. 2. Read the key files. Capture concrete `file:line` references — never vague summaries. 3. If the brief lists `intake_refs`, read those files from the intake folder (`intake.folder`, default `docs/`) — search the docs engine first. Do **not** fetch live sources for intake; if referenced context is missing from the folder, surface the gap (a docs-engine / connector step must add it first). 4. Note: existing patterns/conventions to follow, integration points, risks, and any open questions that would block planning.
Output
Write a concise note to `workspace/features/<slug>/research.md` (or return it inline when standalone) and commit it (`yolo: research <slug>`). Sections: Findings (with file:line), Patterns, Integration points, Risks, Open questions. Keep it tight — this feeds yolo-plan, not a human report.
Constraints
- Read-only: never edit code, never run mutating commands.
- No status files. You do not set or read any feature "status" — that is derived from git (`.claude/yolo/conventions.md`).
- Cite `file:line`; do not invent APIs.
Read more
name: yolo-research description: 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.
yolo-research
Read-only exploration. You gather the context a plan needs; you change nothing.
Inputs
- A brief (`workspace/features/<slug>/brief.md`) — read `goal`, `success_criteria`, `intake_refs`.
Or, when invoked standalone, a plain question.
Procedure
1. Identify the relevant surface: `Glob`/`Grep` for the entities, modules, and routes named in the goal. 2. Read the key files. Capture concrete `file:line` references — never vague summaries. 3. If the brief lists `intake_refs`, read those files from the intake folder (`intake.folder`, default `docs/`) — search the docs engine first. Do **not** fetch live sources for intake; if referenced context is missing from the folder, surface the gap (a docs-engine / connector step must add it first). 4. Note: existing patterns/conventions to follow, integration points, risks, and any open questions that would block planning.
Output
Write a concise note to `workspace/features/<slug>/research.md` (or return it inline when standalone) and commit it (`yolo: research <slug>`). Sections: Findings (with file:line), Patterns, Integration points, Risks, Open questions. Keep it tight — this feeds yolo-plan, not a human report.
Constraints
- Read-only: never edit code, never run mutating commands.
- No status files. You do not set or read any feature "status" — that is derived from git (`.claude/yolo/conventions.md`).
- Cite `file:line`; do not invent APIs.
Ships withyolo
Reasoning-first development for Claude Code. Git is the source of truth; status is derived, never stored. YOLO turns "I want X" into a planned, executed, verified, and landed change, driven by conversation and git rather than tracked status files.
Get the whole plugin
Other skills on yolo.
Skill
yolo-decide
Use when facing a design or architecture decision that benefits from multiple perspectives before committing. Produces a decision record under…
Skill
yolo-feature
Use when the user wants to build, add, or implement a feature. Captures intent, drafts a brief, confirms, then composes research → plan → execute → verify →…
Skill
yolo-finish
Use when a feature is implemented and verified, to land it. Default path is PR + CI check, with the ship gate confirming before the irreversible merge;…
Skill
yolo-init
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/…
Skill
yolo-intake
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…