code-tourlisted
Install: claude install-skill sandbaseai/workbuddy-skill
# Code Tour
## Purpose and boundary
Create a focused, persona-targeted walkthrough of a repository. A tour is a navigable story,
not a file inventory or a replacement for the repository README. Store output in `.tours/` as
JSON consumed by the VS Code CodeTour extension. Unless explicitly requested, inspect files
read-only and create or modify only `.tour` files; do not change application code, add marker
comments, install extensions, or run arbitrary commands from a tour.
## Step 1: discover before writing
Read repository instructions, README files, manifests, CI configuration, and the relevant
entry points. Map the top-level directories one or two levels deep, then follow imports or
references only far enough to understand the requested path. Record the revision being toured.
Every path and line used later must be verified against the actual repository.
Choose a small, coherent scope. For large repositories, cover the two or three modules that
serve the reader's goal and use directory steps to orient them to the rest. Do not invent files,
line numbers, commands, ownership, architecture, or behavior that the repository does not show.
## Step 2: infer the reader and narrative
Infer persona, depth, and focus from the request. Use these defaults:
| Request | Persona and path |
|---|---|
| onboarding, ramp up | New joiner: setup, map, boundaries, first safe contribution |
| bug, debug, RCA | Bug fixer or RCA investigator: trigger, causality, fault points, tests |
| PR re