Agent skill · writing content · alirezarezvani
code-tour
Use when asked for a CodeTour .tour file or a step-by-step code walkthrough (onboarding, architecture, PR review, how X works). Writes persona-targeted steps that link to real files and line numbers, checked to exist.
Why this skill is useful
Adds specific patterns and structured formats for creating CodeTour files that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
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. 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-investigator standard "onboarding" / "new joiner" new-joiner standard "quick tour" / "vibe check" vibecoder quick "architecture" architect deep "security" / "auth review" security-reviewer standard (no qualifier) new-joiner standard When intent is ambiguous, default to new-joiner persona at standard depth — it's the most generally useful. 3. Read actual files Every file path and line number must be verified. A tour pointing to the wrong line is worse than no tour. 4. Write the tour Save to .tours/<persona>-<focus>.tour. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/code-tour--78f1bc