Code Tour
Generate guided CodeTour walkthroughs anchored to real files and lines: onboarding, architecture, PR, and RCA tours.
- What
- Generate guided CodeTour walkthroughs anchored to real files and lines: onboarding, architecture, PR, and RCA tours.
- Cost
- Free
- Needs
- Use "Code Tour" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a method for creating CodeTour `.tour` files, persona-targeted step-by-step walkthroughs that open directly to real files and line ranges. A good tour is a narrative for a specific reader (a new maintainer, a PR reviewer, someone chasing a production incident), telling them what they are looking at, why it matters, and which path to follow next. The skill defines the tour types (onboarding, architecture, PR-review, RCA/security) and the workflow: discover the repo shape first (README, entry points, folder structure, changed files for PR tours), infer the reader, then write the steps as `.tour` JSON in a `.tours/` directory, never modifying source code as part of the skill. It also says when NOT to use a tour: a one-off explanation is better answered directly, prose docs belong elsewhere, and broad onboarding without a tour artifact is a different skill. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: it produces `.tour` JSON files; to experience them as guided in-editor walkthroughs you need the CodeTour VS Code extension (or compatible viewer). Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
Use "Code Tour" with your Muse. Prerequisites: the Muse app (mobile or web), and a repository to tour (local checkout or pasted structure). Produces .tour JSON files; view them with the CodeTour VS Code extension. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/code-tour/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Create a [onboarding / architecture / PR / RCA] tour of [repo path or subsystem], for [a new maintainer / a reviewer / ...]." 3. Ask Muse to discover the repo shape first, then write the .tour steps anchored to real files and line ranges in a .tours/ directory. Tip: name the reader explicitly. A tour written for "everyone" helps no one; a tour for "the new backend maintainer" writes itself. Safety: a skill is plain-text instructions; it runs nothing by itself. Review any file before committing it, never paste secrets into a chat, and review anything Muse proposes before it acts.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.