code-tour

Create CodeTour .tour JSON walkthroughs anchored to real files and line ranges.

4|7|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/arbisoft/ai-skillforge --skill code-tour-arbisoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-tour
Source: https://github.com/arbisoft/ai-skillforge/tree/main/Claude/skills/code-tour
Command: npx skills add https://github.com/arbisoft/ai-skillforge --skill code-tour-arbisoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create CodeTour walkthroughs that open directly to real files and line anchors, enabling precise, shareable codebase tours. Tours live in .tours and follow the CodeTour format, not ad hoc notes.

Core Features & Use Cases

  • Generate .tour JSON artifacts anchored to specific files and lines for onboarding, architecture reviews, PR tours, RCA investigations, and explain-how-this-works sessions.
  • Enforce that tours exist as deterministic, navigable steps and do not modify source code.

Quick Start

Create a new .tour inside .tours anchored to real files using 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 CodeTour walkthrough for repository onboarding?

To create a CodeTour walkthrough for onboarding, generate a .tour JSON artifact stored under the .tours directory, ensuring the tour steps are anchored to specific real files and line ranges within the repository.

Can I use CodeTour for architecture reviews and RCA investigations?

Yes, CodeTour can be used for architecture reviews and RCA investigations by generating deterministic, navigable .tour JSON artifacts that highlight specific code sections without modifying the underlying source code.

What is the best way to document a PR tour using code walkthroughs?

The best way to document a PR tour is to create a CodeTour walkthrough that opens directly to real files and line anchors, generating precise and shareable .tour JSON artifacts for reviewers to follow.

Do I need to install CodeTour to validate anchors against repository files?

You need a CodeTour-compliant environment to validate anchors against repository files, as the Skill requires generating .tour JSON artifacts under the .tours directory and verifying that line ranges map to actual code.

Does generating a code walkthrough modify my source code?

Generating a code walkthrough does not modify your source code; the process strictly enforces that tours exist as deterministic, navigable steps stored as .tour JSON artifacts without altering the original files.

Why should I use .tour JSON artifacts instead of ad hoc notes for codebase tours?

You should use .tour JSON artifacts instead of ad hoc notes because they follow the CodeTour format, ensuring tours are deterministic, navigable, and precisely anchored to real files and line ranges for shareable codebase tours.