kuker24 Code Tour
Write CodeTour JSON under .tours/. Tours open real files and line ranges. Do not modify source as part of this skill.
Boundaries & Handoffs
| Need | Route |
|---|---|
| One-off explanation in chat | answer directly; no tour |
| Prose documentation structure | /technical-writing |
| Implementation or refactor | do the work; do not start a tour |
Reusable .tour walkthrough with file anchors |
code-tour |
Procedure
Consult references/format.md for step types and ref.
- Discover. README, entry points, layout, and (for PR tours) changed files. Do not write steps before the shape is known.
- Infer the reader. New joiner 9–13 steps; quick tour 5–8; architecture 14–18; PR/RCA/security/feature 7–11.
- Verify every anchor. File exists, line in range, selection exact. Prefer a pattern when lines drift. Never guess line numbers.
- Write
.tours/<persona>-<focus>.tour. - Validate. First step is a real file or directory.
refpoints at a revision that actually contains every referenced file. PR tours use the PR branch, never the base.
Each description answers situation, mechanism, implication, gotcha. Narrative: orientation → module map → core path → gotcha → next move.
Output
A valid .tour file plus a one-line confirmation that every path and line was checked against the chosen ref (or against the working tree when ref is omitted).