Code Tour

Use when creating a persona-targeted, step-by-step CodeTour walkthrough that links to real repository files, directories, patterns, and line ranges for onboarding, reviews, debugging, architecture, or contribution guidance.

9 stars 3 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sandbaseai/workbuddy-skill --skill code-tour
Manual install
git clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/code-tour ~/.claude/skills/code-tour

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Code Tour

## Purpose and boundary

Create a focused, persona-targeted walkthrough of a repository. A tour is a navigable story,
not a file inventory or a replacement for the repository README. Store output in `.tours/` as
JSON consumed by the VS Code CodeTour extension. Unless explicitly requested, inspect files
read-only and create or modify only `.tour` files; do not change application code, add marker
comments, install extensions, or run arbitrary commands from a tour.

## Step 1: discover before writing

Read repository instructions, README files, manifests, CI configuration, and the relevant
entry points. Map the top-level directories one or two levels deep, then follow imports or
references only far enough to understand the requested path. Record the revision being toured.
Every path and line used later must be verified against the actual repository.

Choose a small, coherent scope. For large repositories, cover the two or three modules that
serve the reader's goal and use directory steps to orient them to the rest. Do not invent files,
line numbers, commands, ownership, architecture, or behavior that the repository does not show.

## Step 2: infer the reader and narrative

Infer persona, depth, and focus from the request. Use these defaults:

| Request | Persona and path |
|---|---|
| onboarding, ramp up | New joiner: setup, map, boundaries, first safe contribution |
| bug, debug, RCA | Bug fixer or RCA investigator: trigger, causality, fault points, tests |
Read the full skill on GitHub

Details

Skill name
code-tour
Path
skills/code-tour/SKILL.md
License
MIT
Repo updated
8 September 2026

FAQ

What does the Code Tour skill do?

Use when creating a persona-targeted, step-by-step CodeTour walkthrough that links to real repository files, directories, patterns, and line ranges for onboarding, reviews, debugging, architecture, or contribution guidance.

How do I install the Code Tour skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill code-tour. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Code Tour popular?

It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.