code-tourlisted

# Code Tour Generate CodeTour `.tour` JSON files: guided, persona-targeted walkthroughs that open directly to real files and line ranges in any editor with the CodeTour extension. Tours live in `.tours/` at the repo root. ## Usage ``` /code-tour onboarding for the payments service /code-tour architecture tour of src/services /code-tour PR tour for the current branch /code-tour explain the auth middleware for a new joiner ``` ## Behavior ### Phase 1: Discover Explore before writing: README, entry points, folder structure, relevant config, and (for PR tours) the changed files via `git diff --name-only`. Do not draft steps before understanding the shape of the code. ### Phase 2: Infer persona and depth Pick a persona and step count from the request shape: | Request shape | Persona | Steps | | --- | --- | --- | | onboarding, new joiner | `new-joiner` | 9-13 | | quick tour, overview | `quick-look` | 5-8 | | architecture | `architect` | 14-18 | | tour this PR | `pr-reviewer` | 7-11 | | why did this break | `rca-investigator` | 7-11 | | security review | `security-reviewer` | 7-11 | | explain this feature | `feature-explainer` | 7-11 | | debug this path | `bug-fixer` | 7-11 | ### Phase 3: Verify anchors Every anchor must be real. For each candidate `file:line`: ```bash [[ -f "path/to/file" ]] && echo exists wc -l < "path/to/file" # confirm the line number is in range ``` If the file is likely to churn, use a `pattern` step instead of a fixed line. Never guess a line n