Code Tour

This generates CodeTour JSON files that anchor walkthroughs to real file paths and line numbers in your codebase. You'd use it when someone asks for an onboarding tour, a PR walkthrough, or "explain how X works" and you want a reusable artifact instead of a one-off chat answer. The format follows the SMIG rule: situation, mechanism, implication, gotcha, which keeps each step grounded in actual code instead of vague gestures. It's opinionated about persona depth (new joiners get 9-13 steps, vibe checkers get 5-8) and enforces anchor verification before writing. The main trick is that it treats tours as narratives with dependency between steps, not just file inventories with descriptions.

skills.sh installs: 3.6K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill code-tour --agent claude-code

Installs into .claude/skills of the current project.

Files

Code Tour

Create CodeTour .tour files for codebase walkthroughs that open directly to real files and line ranges. Tours live in .tours/ and are meant for the CodeTour format, not ad hoc Markdown notes.

A good tour is a narrative for a specific reader:

what they are looking at
why it matters
what path they should follow next

Only create .tour JSON files. Do not modify source code as part of this skill.

When to Use

Use this skill when:

the user asks for a code tour, onboarding tour, architecture walkthrough, or PR tour
the user says "explain how X works" and wants a reusable guided artifact
the user wants a ramp-up path for a new engineer or reviewer
the task is better served by a guided sequence than a flat summary

Examples: