code-tour

Generate CodeTour .tour JSON artifacts anchored to file and line ranges.

4|Updated Sep 14, 2025
One-click install
npx skills add https://github.com/EvilBit-Labs/DaemonEye --skill code-tour-evilbit-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-tour
Source: https://github.com/EvilBit-Labs/DaemonEye/tree/main/.claude/skills/code-tour
Command: npx skills add https://github.com/EvilBit-Labs/DaemonEye --skill code-tour-evilbit-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CodeTour creates repeatable, anchored walkthroughs that guide developers through a codebase with real file and line anchors, reducing onboarding time and miscommunication.

Core Features & Use Cases

  • Tour artifacts in .tour JSON format to document architecture, PR walkthroughs, RCA tours, and onboarding journeys.
  • Anchored file and line references to open and explore specific code paths during reviews.
  • Reusable, persona-tailored tours that can be shared across teams for consistent knowledge transfer.

Quick Start

Create a .tour file that targets a real file and specifies a starting line to guide a reviewer step-by-step.

Frequently Asked Questions about code-tour

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a guided code walkthrough for onboarding developers to a repository?

To create a guided code walkthrough for onboarding, generate a .tour JSON artifact that anchors steps to real repository files and specific line ranges, guiding developers through code paths sequentially.

What is a CodeTour file and how does it work for architecture reviews?

A CodeTour file is a .tour JSON artifact that documents architecture walkthroughs by validating anchors against real repository files and line ranges, allowing reviewers to explore specific code paths step-by-step.

Can I use anchored file references to document RCA tours and security briefings?

Yes, you can document RCA tours and security briefings by generating .tour JSON artifacts that anchor explanations to real files and line ranges, ensuring reviewers see the exact code paths involved.

Does generating a .tour file require validating line anchors against the codebase?

Yes, generating a .tour file validates anchors against real repository files to ensure line ranges and file paths exist, preventing broken walkthroughs during PR tours and architecture reviews.

What's the best way to share reusable code walkthroughs across a development team?

The best way to share reusable code walkthroughs is creating persona-tailored .tour JSON artifacts anchored to real files, enabling consistent knowledge transfer and architecture onboarding across teams.

When should I not use CodeTour artifacts for documenting a codebase?

You should not use CodeTour artifacts when a codebase lacks stable file paths or line ranges, as the .tour JSON format requires validating anchors against real repository files to function correctly.