Code Tour
- 4.2k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/everything-claude-code
A CodeTour `.tour` JSON file containing a sequence of steps, each with file path, line range, and narrative explanation, that guides a persona through a codebase segment.
About
This skill generates CodeTour `.tour` JSON files that create guided, interactive walkthroughs of codebases. Developers use it to build onboarding tours, architecture walkthroughs, PR reviews, and root-cause analysis tours that link directly to specific files and line ranges. Each tour targets a persona (e.g., new-joiner) and tells a narrative explaining what code does, why it matters, and what to explore next. Tours live in `.tours/` directories and serve as reusable artifacts rather than ad-hoc markdown. The skill starts with codebase exploration - README, structure, config files - then constructs step-by-step sequences (9-13 steps for onboarding) without modifying source code. Generate CodeTour `.tour` JSON files with file paths, line anchors, and explanations. Target specific personas (new-joiner, reviewer, architect) with appropriate depth and narrative. Discover repo structure, entry points, and modified files before writing steps.
- Generate CodeTour `.tour` JSON files with file paths, line anchors, and explanations
- Target specific personas (new-joiner, reviewer, architect) with appropriate depth and narrative
- Discover repo structure, entry points, and modified files before writing steps
- Create reusable guided sequences for onboarding, architecture, PR, and RCA contexts
- Store tours in `.tours/` directories; never modify source code as part of skill
Code Tour by the numbers
- 4,189 all-time installs (skills.sh)
- +219 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #98 of 1,879 Documentation skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
code-tour capabilities & compatibility
- Capabilities
- explore codebase structure and entry points · map file relationships and data flow · generate codetour json with anchors · tailor depth and persona to request
- Use cases
- documentation · code review · research
- Platforms
- macOS · Windows · Linux
- Runs
- Runs locally
npx skills add https://github.com/affaan-m/everything-claude-code --skill code-tourAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 4.2k |
|---|---|
| repo stars | ★ 238k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 5, 2026 |
| Repository | affaan-m/everything-claude-code ↗ |
What it does
Create structured CodeTour .tour files to guide developers through codebase walkthroughs with file anchors and line ranges.
Who is it for?
Onboarding new engineers, PR reviews, architecture explanations, RCA walkthroughs, structured 'how does X work' requests, ramp-up paths for contributors.
Skip if: One-time explanations, professional documentation edits, implementation or refactoring work, broad codebase onboarding (use codebase-onboarding skill).
When should I use this skill?
User requests code tour, onboarding tour, architecture walkthrough, PR tour, or structured guided explanation with reusable artifact intent.
What you get
Reusable, interactive `.tour` files stored in `.tours/` that let developers step through code with context-aware narration and direct file/line anchors.
- .tour JSON files
- onboarding walkthrough
- architecture tour steps
By the numbers
- Onboarding tours: 9-13 steps recommended
- Tour format: JSON with file path, line range, and step description per entry
- Storage: `.tours/` directory convention
Files
コードツアー
コードベースウォークスルー用のCodeTour .tourファイルを作成し、実際のファイルとラインの範囲に直接開きます。ツアーは.tours/にあり、アドホックなMarkdownノートではなくCodeTour形式を対象としています。
良いツアーは特定の読者への物語：
- 彼らが何を見ているか
- なぜそれが重要か
- 次にどのパスを従うべきか
.tour JSONファイルのみを作成。このスキルの一部としてソースコードを変更しないでください。
使用時期
次の場合にこのスキルを使用：
- ユーザーがコードツアー、オンボーディングツアー、アーキテクチャウォークスルー、またはPRツアーを求める
- ユーザーが「Xがどのように機能するかを説明」と言い、再利用可能なガイド付きアーティファクトを望む
- 新しいエンジニアまたはレビュアーのためのランプアップパス
- タスクはフラット概要ではなくガイド付きシーケンスでより良くサービスされる
使用しないとき
| コードツアーの代わりに | 使用 |
|---|---|
| 一度限りの説明で十分 | 直接答える |
ユーザーがプロのドキュメント、.tourアーティファクトではなく | ドキュメント編集 |
| タスクは実装またはリファクタリング | 実装作業を行う |
| 広範なコードベースオンボーディング | codebase-onboarding |
ワークフロー
1. 発見
何か書く前にリポを探索：
- READMEとパッケージ/アプリエントリポイント
- フォルダ構造
- 関連するコンフィグファイル
- ツアーがPRフォーカスの場合は変更されたファイル
コードの形状を理解する前にステップを書き始めないでください。
2. 読者を推測
要求からペルソナと深さを決定。
| リクエストの形 | ペルソナ | 推奨される深さ |
|---|---|---|
| 「オンボーディング」「新しい参加者」 | new-joiner | 9-13ステップ |
ツアー形式
Code Tour .tourファイルはJSON形式で、各ステップはファイルパス、ライン番号、説明を含みます。
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71Forks & variants (1)
Code Tour has 1 known copy in the catalog totaling 1.4k installs. They canonicalize to this original listing.
- affaan-m - 1.4k installs
FAQ
When should I use CodeTour instead of writing direct documentation?
Use CodeTour when the guide benefits from stepping through actual code with line anchors and a narrative sequence. Use docs for reference material or when users prefer flat overviews.
How many steps should a tour have?
Onboarding tours typically 9-13 steps. Adjust based on persona depth: new-joiner is comprehensive, architect-review is focused on key design points.
Should I modify source code as part of creating a tour?
No. Create only `.tour` JSON files in `.tours/` directories. Never change source code; the skill is about guiding through existing code.
Is Code Tour safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.