code-tour

Create JSON CodeTour artifacts with anchored file and line references.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/sakamoto-family-smile/agent_monorepo --skill code-tour-sakamoto-family-smile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-tour
Source: https://github.com/sakamoto-family-smile/agent_monorepo/tree/main/.claude/skills/ecc/code-tour
Command: npx skills add https://github.com/sakamoto-family-smile/agent_monorepo --skill code-tour-sakamoto-family-smile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CodeTour creation enables precise, anchored codebase walkthroughs that accelerate onboarding and architecture reviews.

Core Features & Use Cases

  • Tour files provide guided, anchored walks directly to real files and line ranges.
  • Use cases include onboarding new engineers, architecture reviews, PR tours, RCA tours, and security reviews.

Quick Start

Create a .tour file under .tours/ that anchors real files and line ranges for a guided code walkthrough.

Frequently Asked Questions about code-tour

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

FAQPage Schema
How do I create a guided code walkthrough for onboarding new engineers?

Create a guided code walkthrough by generating JSON CodeTour artifacts under the .tours directory, defining steps that anchor directly to real files and exact line ranges to accelerate onboarding without modifying source code.

Can I use CodeTour files for PR reviews and architecture walkthroughs?

CodeTour files support PR reviews, architecture walkthroughs, RCA tours, and security reviews by guiding readers through anchored file selections and precise line ranges within the codebase.

What is the best way to anchor real files and line ranges in a codebase tour?

Anchor real files and line ranges in a codebase tour by creating JSON artifacts stored under .tours, where each step references specific file paths and anchored selections to guide readers through the code.

Does creating a code walkthrough tour modify the source code?

Creating a code walkthrough tour does not modify source code; it requires only JSON CodeTour artifacts stored under .tours with steps that reference real files and anchored selections.

How do CodeTour artifacts work for guiding readers through a codebase?

CodeTour artifacts work as JSON files stored under .tours that provide guided, anchored walks directly to real files and line ranges, enabling readers to navigate codebase architecture step by step.

What do I need to set up before creating anchored codebase walkthroughs?

To create anchored codebase walkthroughs, you need a .tours directory in your repository to store JSON CodeTour artifacts and real source files with identifiable line ranges to anchor the tour steps.