code-tour

原文涵盖的主题

• Code Tour
• When to Use
• When NOT to Use
• Workflow
• 1. Discover
• 2. Infer the reader
• 3. Read and verify anchors
• 4. Write the .tour

Create CodeTour .tour files for codebase walkthroughs that open directly to real files and line ranges. Tours live in .tours/ and are meant for the CodeTour format, not ad hoc Markdown notes. A good tour is a narrative for a specific reader: what they are looking at why it matters what path they should follow next Only create .tour JSON files. Do not modify source code as part of this skill. Use this skill when: the user asks for a code tour, onboarding tour, architecture walkthrough, or PR tour the user says "explain how X works" and wants a reusable guided artifact the user wants a ramp-up path for a new engineer or reviewer the task is better served by a guided sequence than a flat summary Examples: onboarding a new maintainer architecture tour for one service or package PR-review walk-through anchored to changed files RCA tour showing the failure path security review tour of trust boundaries and key checks | Instead of code-tour | Use | | --- | --- | | A one-off explanation in chat is enough | answer directly | | The user wants prose docs, not a .tour artifact | documentation-lookup or repo docs editing | | The task is implementation or refactoring | do the implementation work

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