code-tour

Create CodeTour walkthroughs anchored to specific files and lines.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Patasse97/claude-skills --skill code-tour-patasse97
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-tour
Source: https://github.com/Patasse97/claude-skills/tree/main/engineering/code-tour
Command: npx skills add https://github.com/Patasse97/claude-skills --skill code-tour-patasse97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebases often require structured, navigable walkthroughs to onboard contributors, review changes, and explain architecture. This skill provides a standardized way to generate CodeTour files that anchor to real files and lines, enabling precise and repeatable code tours.

Core Features & Use Cases

  • Create .tour JSON files that link to specific files and line numbers within a repository.
  • Support all CodeTour step types (Content, Directory, File+Line, Selection, Pattern, URI) and enforce the SMIG narrative framework for coherent tours.
  • Save tours to .tours/<persona>-<focus>.tour to organize tours by persona and purpose, making onboarding, PR reviews, architecture walkthroughs, and tutorials easier.

Quick Start

Save the tour to .tours/<persona>-<focus>.tour and populate with validated steps following the CodeTour schema.

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 code walkthrough that links to specific files and line numbers in my repository?▼

You can create a code walkthrough by generating .tour JSON files that anchor steps to specific files and lines. This provides a structured, navigable path through repository code for onboarding, PR reviews, and architecture explanations.

What is the SMIG narrative structure for code walkthroughs?▼

The SMIG narrative framework is a storytelling structure enforced during tour generation to ensure coherent, step-by-step code walkthroughs. It guides the creation of CodeTour steps so that onboarding guides and architecture explanations flow logically.

Can I use CodeTour for pull request reviews and contributor onboarding?▼

Yes, CodeTour supports pull request reviews, contributor onboarding, and architecture explanations. Tours are saved as JSON files in a .tours directory, organized by persona and focus to streamline the review and onboarding process.

What CodeTour step types are supported for repository code walkthroughs?▼

Supported step types include Content, Directory, File+Line, Selection, Pattern, and URI. These types allow tours to anchor to specific repository locations, validate real file paths, and provide precise, context-aware walkthroughs.

How are generated CodeTour files organized and saved within a project?▼

Generated CodeTour files are saved as JSON files within a .tours directory. They follow a <persona>-<focus>.tour naming convention, organizing walkthroughs by target audience and specific purpose like onboarding or architecture.