Agent skill · writing content · borghei
code-tour
Build ordered, annotated tours of an unfamiliar codebase and keep the anchors from rotting. Use when onboarding an engineer, handing off a service, or explaining a subsystem before a review.
Why this skill is useful
Provides a structured workflow for creating annotated codebase tours, enhancing onboarding and knowledge transfer.
What it needs
Requires python3 installed locally. About 8k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Code Tour A guided path through a codebase, ordered so each stop makes the next one legible, and annotated with why the code is the way it is rather than what it does. The what is already on screen; the why is what takes a new engineer three weeks to reconstruct and what the person who knows it will lose in six months. Tours rot faster than any other documentation because they point at line numbers, so anchoring and validation are half this skill. When to use this skill Onboarding an engineer onto a service where reading order determines whether week one is productive or archaeological Handing off ownership of a system before its author changes team or leaves Explaining a subsystem ahead of a design review, so reviewers arrive with shared context Documenting a surprising design whose rationale lives only in a closed pull request Auditing an existing tour that has silently rotted as files moved and functions were renamed Re-entering your own code after six months away, which is functionally the same problem as onboarding Inputs the skill expects The repository root, and which directories are vendored or generated The audience and their starting knowledge — a backend engineer and a frontend engineer need different first stops The one question the tour must leave answered ("how does a request become a row?") Time budget, which sets the stop count more than anything else The design decisions worth explaining, especially the ones that look wrong at first glance An existing tour definition, when validating or updating rather than authoring Clarify First Before building the tour, confirm these inputs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/code-tour