code-tour

Create .tour JSON artifacts anchored to files and line ranges for codebase walkthroughs.

86|21|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill code-tour-jamkris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-tour
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/code-tour
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill code-tour-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CodeTour enables creating .tour files that provide guided, narrative codebase walkthroughs anchored to real files and specific line ranges, improving onboarding and code review efficiency.

Core Features & Use Cases

  • Tour artifacts: produce .tour JSON files that open exact files/lines for readers.
  • Onboarding & architecture reviews: support step-by-step introductions and PR tours.
  • Guided explanations: provide a reusable narrative for explain-how-this-works requests.

Quick Start

Create a .tour file anchored to a real file with line references to guide a new engineer.

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 for onboarding new engineers?

CodeTour artifacts are .tour JSON files that anchor narrative steps to real files and specific line ranges. They support onboarding, architecture walkthroughs, PR tours, RCA reviews, and explain-how-this-works requests across software projects.

How do I make a code tour anchored to actual line numbers in my repository?

To generate a .tour file, create a JSON artifact anchored to a real file with specific line references. This guides readers by opening exact files and lines, enforcing that anchors point to existing code files without modifying source.

Do I need to modify my source code to add a guided code walkthrough?

No, you do not need to modify your source code to add a guided code walkthrough. The process requires anchoring to existing code files and produces only .tour JSON artifacts, leaving the original source unmodified.

Can I use code tours for PR reviews and RCA documentation?

You can use code tours for PR reviews and RCA documentation because the .tour artifacts explicitly support PR tours, RCA reviews, architecture walkthroughs, and explain-how-this-works requests across software projects.

What are the limitations of using .tour JSON artifacts for codebase walkthroughs?

A limitation of using .tour JSON artifacts is that they strictly produce only .tour JSON files and require anchoring to existing code files. They do not modify source code directly within the repository.