code-tour

Create CodeTour .tour JSON files with anchored walkthroughs in .tours directories.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/khunglong-03/Pathora_Version3 --skill code-tour-khunglong-03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-tour
Source: https://github.com/khunglong-03/Pathora_Version3/tree/main/.cursor/skills/code-tour
Command: npx skills add https://github.com/khunglong-03/Pathora_Version3 --skill code-tour-khunglong-03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CodeTour files provide guided, anchor-based 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.

Core Features & Use Cases

  • Anchored walkthroughs: Tours open to precise files and line ranges, enabling targeted code review or onboarding.
  • Tour storage: Tours are organized under .tours/ as CodeTour JSON artifacts.
  • Use cases: Onboarding new engineers, architecture walkthroughs, PR tour explanations, RCA tours, and explain-how-this-works requests.

Quick Start

Create a CodeTour under .tours with a .tour JSON file anchored to real files and lines.

Frequently Asked Questions about code-tour

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create guided code walkthroughs anchored to specific files and line numbers?

Guided code walkthroughs are created as CodeTour .tour JSON files stored in the .tours directory, containing anchor references to precise file paths and line ranges for targeted onboarding and architecture reviews.

What is the best way to onboard new engineers to a complex codebase?

The best way to onboard new engineers is generating CodeTour .tour files that provide narrative-driven, anchor-based walkthroughs opening directly to real files, explaining what they are looking at, why it matters, and what path to follow next.

Can I use anchored code tours for pull request reviews and RCA explanations?

Yes, anchored code tours support pull request explanations and root cause analysis walkthroughs by creating .tour JSON artifacts that open directly to relevant file paths and line ranges without modifying the source code.

Does the CodeTour format require modifying source code to add documentation?

No, the CodeTour format requires creating only JSON .tour artifacts under the .tours directory and explicitly avoids modifying source code, ensuring documentation remains separate from the codebase.

What are the limitations of using .tour JSON files for codebase documentation?

Limitations include being restricted to the CodeTour JSON format stored in .tours directories, meaning these anchored walkthroughs cannot serve as ad hoc Markdown notes or modify source code directly.

When do I need anchor-based code tours instead of standard markdown documentation?

You need anchor-based code tours when providing guided, line-specific walkthroughs for onboarding, architecture reviews, or explain-how-this-works scenarios, rather than ad hoc Markdown notes unattached to specific code locations.