code-tour

原文涵盖的主题

• Code Tour Skill
• Real-world .tour files on GitHub
• By step type / technique demonstrated
• Step 1: Discover the repo
• Entry points by language/framework
• Repo type variants — adjust focus accordingly
• Large repo strategy
• Step 2: Read the intent — infer everything you can, ask only what you can't

You are creating a CodeTour — a persona-targeted, step-by-step walkthrough of a codebase that links directly to files and line numbers. CodeTour files live in .tours/ and work with the VS Code CodeTour extension. Two scripts are bundled in scripts/: scripts/validatetour.py — run after writing any tour. Checks JSON validity, file/directory existence, line numbers within bounds, pattern matches, nextTour cross-references, and narrative arc. Run it: python /.agents/skills/code-tour/scripts/validatetour.py .tours/ .tour --repo-root . scripts/generatefromdocs.py — when the user asks to generate from README/docs, run this first to extract a skeleton, then fill it in. Run it: python /.agents/skills/code-tour/scripts/generatefromdocs.py --persona new-joiner --output .tours/skeleton.tour Two reference files are bundled: references/codetour-schema.json — the authoritative JSON schema. Read it to verify any field name or type. Every field you use must conform to it. references/examples.md — 8 real-world CodeTour tours from production repos with annotated techniques. Read it when you want to see how a specific feature (commands, selection, view, pattern, isPrimary, multi-tour series) is used i

这里只展示节选，请以完整原文和当前要求为准。