borghei/Claude-Skills / engineering/code-tour
code-tour
VerifiedBuild 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.3 KB |
| assets/sample_tour.json | config | 5.1 KB |
| assets/tour-template.json | config | 1.3 KB |
| references/tour-construction.md | markdown | 8.5 KB |
| references/tour-maintenance.md | markdown | 8.5 KB |
| scripts/tour_propose.py | script | 9.6 KB |
| scripts/tour_render.py | script | 7.2 KB |
| scripts/tour_validate.py | script | 10.0 KB |
assets/tour-template.json
View on GitHub{
"title": "<what this tour teaches, phrased as the question it answers>",
"repo": ".",
"audience": "<who is reading — backend engineer, frontend engineer, SRE, contractor>",
"duration_minutes": 30,
"orientation": "Two to four sentences the reader takes in before opening any file: what the system does, what ordering principle the stops follow, and what they should be able to do at the end. Say here if the tour can be run locally.",
"prerequisites": [
"<tool or access needed to follow along>",
"<document to read first, if any>"
],
"stops": [
{
"stop": 1,
"title": "<what the reader learns here, not the filename>",
"path": "<path/from/repo/root.py>",
"anchor": "<function_or_class_name>",
"line": 0,
"fingerprint": "",
"read_first": "<optional: what to look at before the note makes sense>",
"note": "Why this code is the way it is. Answer at least one of: why does this exist, why this way and not the obvious alternative, what breaks if you change it. Aim for 50-80 words. Do not describe what the code does — the reader can see that.",
"question": "<a question the reader can only answer by reading the code at this stop>",
"gotcha": "<optional: the thing that surprises everyone here>"
}
],
"after": "<what to do next — a first task, a script to run, a second tour>"
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |