code-tour

# Code Tour Create **CodeTour** files — persona-targeted, step-by-step walkthroughs of a codebase that link directly to files and line numbers. CodeTour files live in `.tours/` and work with the [VS Code CodeTour extension](https://github.com/microsoft/codetour). ## Overview A great tour is a **narrative** — a story told to a specific person about what matters, why it matters, and what to do next. Only create `.tour` JSON files. Never modify source code. ## When to Use This Skill - User asks to create a code tour, onboarding tour, or architecture walkthrough - User says "tour for this PR", "explain how X works", "vibe check", "RCA tour" - User wants a contributor guide, security review, or bug investigation walkthrough - Any request for a structured walkthrough with file/line anchors ## Core Workflow ### 1. Discover the repo Before asking anything, explore the codebase: In parallel: list root directory, read README, check config files. Then: identify language(s), framework(s), project purpose. Map folder structure 1-2 levels deep. Find entry points — every path in the tour must be real. If the repo has fewer than 5 source files, create a quick-depth tour regardless of persona — there's not enough to warrant a deep one. ### 2. Infer the intent One message should be enough. Infer persona, depth, and focus silently. | User says | Persona | Depth | |-----------|---------|-------| | "tour for this PR" | pr-reviewer | standard | | "why did X break" / "RCA" | rca-invest...