code-tour

Generate CodeTour JSON files anchored to exact files and line ranges.

2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill code-tour-momodaviluke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-tour
Source: https://github.com/MomoDaviluke/star-citizen-promotion/tree/main/.agents/skills/ecc/code-tour
Command: npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill code-tour-momodaviluke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to onboard newcomers and reason about large codebases without guided, reproducible walkthroughs. This Skill creates CodeTour artifacts that anchor to real files and line ranges, enabling focused, repeatable explorations.

Core Features & Use Cases

  • Create CodeTour .tour JSON files that open to exact files and line ranges for targeted walkthroughs.
  • Store tours under the .tours/ directory and use the official CodeTour format, not ad hoc notes.
  • Use for onboarding, architecture reviews, PR tours, RCA tours, and explain-how-this-works sessions to reduce ramp time and improve reviews.

Quick Start

Create a .tour in the .tours directory that anchors to real files and line ranges for an onboarding 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 guided code walkthroughs for onboarding new engineers?

Guided code walkthroughs for onboarding are created by generating CodeTour .tour JSON files that anchor to exact files and line ranges, delivering structured, repeatable tours stored in the .tours directory.

What is a CodeTour artifact and how does it help with architecture reviews?

A CodeTour artifact is a JSON file that opens to specific files and line ranges, providing a reproducible walkthrough to guide engineers through architecture reviews and reduce ramp time without modifying source code.

How do I document a pull request or root cause analysis tour in a complex codebase?

You document a PR tour or RCA tour by creating a .tour JSON file that anchors to real files and line ranges, enabling focused, repeatable explorations of the exact code changes or failure points without ad hoc notes.

Can I create code walkthroughs without modifying the actual source code?

Yes, you can create code walkthroughs without modifying source code because the tour creation process strictly prohibits altering the original files, instead storing all walkthrough data as JSON artifacts in the .tours directory.

What is the best way to ensure my code walkthroughs follow a standard format?

The best way to ensure standard code walkthroughs is to use the official CodeTour JSON format, which structures your tours as .tour files stored consistently under the .tours directory for repeatable explorations.