Agent skill

Code Tour

Create CodeTour .tour files — persona-targeted, step-by-step walkthroughs with real file and line anchors.

MITAuto-check passedDevelopment

Install Code Tour

skills CLI

$ npx skills add affaan-m/ECC --skill code-tour -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC code-tour --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/code-tour .claude/skills/code-tour && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "code-tour" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/code-tour into .claude/skills/code-tour/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-tour", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/affaan-m/ECC/tree/main/skills/code-tour

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add affaan-m/ECC --skill code-tour -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC code-tour --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/code-tour .agents/skills/code-tour && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "code-tour" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/code-tour into .agents/skills/code-tour/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-tour", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add affaan-m/ECC --skill code-tour -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC code-tour --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/code-tour .cursor/skills/code-tour && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "code-tour" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/code-tour into .cursor/skills/code-tour/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-tour", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/affaan-m/ECC.git --path skills/code-tour

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add affaan-m/ECC --skill code-tour -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC code-tour --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/code-tour .gemini/skills/code-tour && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "code-tour" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/code-tour into .gemini/skills/code-tour/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-tour", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install affaan-m/ECC code-tour

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add affaan-m/ECC --skill code-tour -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/code-tour .github/skills/code-tour && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "code-tour" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/code-tour into .github/skills/code-tour/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-tour", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add affaan-m/ECC --skill code-tour -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC code-tour --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/code-tour .opencode/skills/code-tour && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "code-tour" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/code-tour into .opencode/skills/code-tour/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-tour", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: code-tour
GitHub stars: 276k
Used in: 1 other repo
Token cost: ~2k tokens
SKILL.md length: 900 words
Files: 1
Skills in repo: 673
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Create CodeTour .tour files — persona-targeted, step-by-step walkthroughs with real file and line anchors.

Works in 5 steps: Discover → Infer the reader → Read and verify anchors → …
Onboarding tours
SKILL.md covers When to Use, When NOT to Use, Workflow and The ref Field, plus 7 more sections
Reaches github.com and aka.ms

What it does

Code Tour is an agent skill from affaan-m/ECC. Create CodeTour .tour files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests. Use when the user asks for a code tour, onboarding walkthrough, PR tour, or an explanation of how a subsystem works.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Codebase onboarding. The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

Onboarding tours
Architecture walkthroughs
Structured explain how this works requests
The user asks for a code tour

Example prompts

“explain how this works”
“/code-tour”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Discover
Infer the reader
Read and verify anchors
Write the .tour
Validate

What it can do on your machine

Read from SKILL.md and the folder at commit ef648e0. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
- aka.ms
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Code Tour loads about 2k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 900 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~90
When it runs · the whole SKILL.md, loaded when a task matches: ~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit ef648e0, republished under its MIT licence (© affaan-m). 900 words, ~2,006 tokens.

Download SKILL.mdSave it as .claude/skills/code-tour/SKILL.md (or your agent's skills folder).

name: code-tour
description: Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests. Use when the user asks for a code tour, onboarding walkthrough, PR tour, or an explanation of how a subsystem works.
metadata.origin: ECC

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:

onboarding a new maintainer
architecture tour for one service or package
PR-review walk-through anchored to changed files
RCA tour showing the failure path
security review tour of trust boundaries and key checks

When NOT to Use

Instead of code-tour	Use
A one-off explanation in chat is enough	answer directly
The user wants prose docs, not a `.tour` artifact	`documentation-lookup` or repo docs editing
The task is implementation or refactoring	do the implementation work
The task is broad codebase onboarding without a tour artifact	`codebase-onboarding`

Workflow

1. Discover

Explore the repo before writing anything:

README and package/app entry points
folder structure
relevant config files
the changed files if the tour is PR-focused

Do not start writing steps before you understand the shape of the code.

2. Infer the reader

Decide the persona and depth from the request.

Request shape	Persona	Suggested depth
"onboarding", "new joiner"	`new-joiner`	9-13 steps
"quick tour", "vibe check"	`vibecoder`	5-8 steps
"architecture"	`architect`	14-18 steps
"tour this PR"	`pr-reviewer`	7-11 steps
"why did this break"	`rca-investigator`	7-11 steps
"security review"	`security-reviewer`	7-11 steps
"explain how this feature works"	`feature-explainer`	7-11 steps
"debug this path"	`bug-fixer`	7-11 steps

3. Read and verify anchors

Every file path and line anchor must be real:

confirm the file exists
confirm the line numbers are in range
if using a selection, verify the exact block
if the file is volatile, prefer a pattern-based anchor

Never guess line numbers.

4. Write the `.tour`

Write to:

text

.tours/<persona>-<focus>.tour

Keep the path deterministic and readable.

5. Validate

Before finishing:

every referenced path exists
every line or selection is valid
the first step is anchored to a real file or directory
the ref points at a branch or commit that actually has every file the tour references (see below)
the tour tells a coherent story rather than listing files

The `ref` Field

ref ties the tour to a git branch or commit. It matters more than it looks: when ref is not the branch the reader has checked out, CodeTour opens each step's file from that revision in git, not from the files on disk. If a file is not in that revision, the step will not open — the reader sees "The editor could not be opened because the file was not found" even though the file is sitting right there. The tour and its comments still show, so the real cause is easy to miss.

Pick ref by tour type:

Tour type	Set `ref` to
PR tour	the PR branch — never the base branch
Onboarding / architecture	the branch the reader will be on (often `main`), or leave it out
Not sure	leave `ref` out, so CodeTour reads files straight from disk

The PR case is the common trap: a PR usually adds new files, and new files do not exist on the base branch yet. Point ref at the base (e.g. develop) and every step on a new file fails to open.

Before finishing, confirm each step's file actually exists at the ref you chose.

Show full SKILL.md (269 more words)Show less

Step Types

Content

Use sparingly, usually only for a closing step:

json

{ "title": "Next Steps", "description": "You can now trace the request path end to end." }

Do not make the first step content-only.

File + line

This is the default step type:

json

{ "file": "src/auth/middleware.ts", "line": 42, "title": "Auth Gate", "description": "Every protected request passes here first." }

Selection

Use when one code block matters more than the whole file:

json

{
  "file": "src/core/pipeline.ts",
  "selection": {
    "start": { "line": 15, "character": 0 },
    "end": { "line": 34, "character": 0 }
  },
  "title": "Request Pipeline",
  "description": "This block wires validation, auth, and downstream execution."
}

Pattern

Use when exact lines may drift:

json

{ "file": "src/app.ts", "pattern": "export default class App", "title": "Application Entry" }

URI

Use for PRs, issues, or docs when helpful:

json

{ "uri": "https://github.com/org/repo/pull/456", "title": "The PR" }

Writing Rule: SMIG

Each description should answer:

Situation: what the reader is looking at
Mechanism: how it works
Implication: why it matters for this persona
Gotcha: what a smart reader might miss

Keep descriptions compact, specific, and grounded in the actual code.

Narrative Shape

Use this arc unless the task clearly needs something different:

orientation
module map
core execution path
edge case or gotcha
closing / next move

The tour should feel like a path, not an inventory.

Example

json

{
  "$schema": "https://aka.ms/codetour-schema",
  "title": "API Service Tour",
  "description": "Walkthrough of the request path for the payments service.",
  "ref": "main",
  "steps": [
    {
      "directory": "src",
      "title": "Source Root",
      "description": "All runtime code for the service starts here."
    },
    {
      "file": "src/server.ts",
      "line": 12,
      "title": "Entry Point",
      "description": "The server boots here and wires middleware before any route is reached."
    },
    {
      "file": "src/routes/payments.ts",
      "line": 8,
      "title": "Payment Routes",
      "description": "Every payments request enters through this router before hitting service logic."
    },
    {
      "title": "Next Steps",
      "description": "You can now follow any payment request end to end with the main anchors in place."
    }
  ]
}

Anti-Patterns

Anti-pattern	Fix
Flat file listing	Tell a story with dependency between steps
Generic descriptions	Name the concrete code path or pattern
Guessed anchors	Verify every file and line first
Too many steps for a quick tour	Cut aggressively
First step is content-only	Anchor the first step to a real file or directory
Persona mismatch	Write for the actual reader, not a generic engineer

Best Practices

keep step count proportional to repo size and persona depth
use directory steps for orientation, file steps for substance
for PR tours, cover changed files first
for monorepos, scope to the relevant packages instead of touring everything
close with what the reader can now do, not a recap

codebase-onboarding
coding-standards
council
official upstream format: microsoft/codetour

Files

Just SKILL.md in skills/code-tour of affaan-m/ECC.

Open the folder on GitHubat commit ef648e0

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 7, 2026.

templetongroup/radiantskills/code-tour

Compare with similar skills

Code Tour next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Code Tour compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Code Tour this skillaffaan-m/ECC	276k	1 repos	~2k	Automated safety check: Pass	MIT	4 days ago
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything	86k	—	~1.2k	Automated safety check: Pass	MIT	today
Understand ExplainEgonex-AI/Understand-Anything	86k	—	~1.3k	Automated safety check: Pass	MIT	today
Project Onboarding Guide from Knowledge GraphEgonex-AI/Understand-Anything	86k	—	~1.2k	Automated safety check: Pass	MIT	today
GitDiagram Repository Overviewahmedkhaleel2004/gitdiagram	18k	—	~427	Automated safety check: Pass	MIT	today
Deepwiki Rssopaco/deepwiki-rs	3.1k	—	~748	Automated safety check: Pass	MIT	25 days ago

Similar skills

Codebase Knowledge Graph Q&A
Egonex-AI/Understand-Anything
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
86k GitHub stars~1.2k tokensUpdated today
DevelopmentAuto-check passed
Understand Explain
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
86k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
Project Onboarding Guide from Knowledge Graph
Egonex-AI/Understand-Anything
Writes an onboarding guide for new team members from a project's existing knowledge graph, after checking that the graph still matches the current commit.
86k GitHub stars~1.2k tokensUpdated today
DevelopmentAuto-check passed
GitDiagram Repository Overview
ahmedkhaleel2004/gitdiagram
Explains the architecture of a public GitHub repository through GitDiagram: how the code is organized, the main components with paths, and a Mermaid diagram.
18k GitHub stars~427 tokensUpdated today
DevelopmentAuto-check passed
Deepwiki Rs
sopaco/deepwiki-rs
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation.
3.1k GitHub stars~748 tokensUpdated 25 days ago
DevelopmentAuto-check passed
Explore Codebase with Graph
tirth8205/code-review-graph
Navigates a codebase through the code-review-graph MCP tools: architecture overview, symbol search, caller and callee tracing, flows and oversized functions.
32k GitHub starsUsed in 1 repo~335 tokens
DevelopmentAuto-check passed

Questions about Code Tour

What does Code Tour do?

Create CodeTour .tour files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Code Tour is an agent skill from affaan-m/ECC.tour files — persona-targeted, step-by-step walkthroughs with real file and line anchors.

When should I use Code Tour?

Code Tour fits situations like: onboarding tours; architecture walkthroughs; structured explain how this works requests; the user asks for a code tour.

How do I install Code Tour in Claude Code?

Run `npx skills add affaan-m/ECC --skill code-tour -a claude-code`. Or copy the skill folder (skills/code-tour in affaan-m/ECC) into .claude/skills/code-tour in your project. Claude Code loads it when a task matches its description.

How do I install Code Tour in Codex?

Run `npx skills add affaan-m/ECC --skill code-tour -a codex`. Or copy the skill folder (skills/code-tour in affaan-m/ECC) into .agents/skills/code-tour in your project. Codex loads it when a task matches its description.

Can I use Code Tour in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill code-tour -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-tour, .gemini/skills/code-tour, .github/skills/code-tour and .opencode/skills/code-tour in your project.

What does Code Tour need to run?

SKILL.md names no scripts, command-line tools or credentials: Code Tour is instructions for the agent only.

Does Code Tour access the network?

SKILL.md names 2 domains. In commands or code: github.com and aka.ms; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Code Tour safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Code Tour use?

Code Tour is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Tour use?

About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Code Tour?

Skills that share tags, products or a category with Code Tour: Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 86k stars), Understand Explain (Egonex-AI/Understand-Anything, 86k stars), Project Onboarding Guide from Knowledge Graph (Egonex-AI/Understand-Anything, 86k stars) and GitDiagram Repository Overview (ahmedkhaleel2004/gitdiagram, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Tour?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 275,546 GitHub stars. The repository holds 673 skills in this directory. The repository was last updated on October 5, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Code Tour

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Code Tour

When to Use

When NOT to Use

Workflow

1. Discover

2. Infer the reader

3. Read and verify anchors

4. Write the .tour

5. Validate

The ref Field

Step Types

Content

Directory

File + line

Selection

Pattern

URI

Writing Rule: SMIG

Narrative Shape

Example

Anti-Patterns

Best Practices

Related Skills

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from affaan-m/ECC

Related

Questions about Code Tour

4. Write the `.tour`

The `ref` Field