Code Tour
Use when the user asks to create a CodeTour .tour file — persona-targeted, step-by-step walkthroughs that link to real files and line numbers.
Before & after
Same prompt, same agent — the only difference is the skill.
That's a great idea for onboarding. Creating a CodeTour walkthrough would be helpful, but I'd need to understand your codebase structure first. Which parts are most important for new developers to understand? Is there a particular feature or flow that tends to confuse new people? How many steps do you think the tour should be—something quick, or more comprehensive? I can help you organize the files and explain them, but I'd want to make sure we're covering the right areas. Maybe we could start with a brief overview and then dive into specific components? Let me know what would be most useful.
CODETOUR CREATED: Backend Onboarding (15 steps) FILE: .vscode/extensions/codetour.tour TARGET AUDIENCE: Junior backend engineers TOUR STRUCTURE: STEP 1: Entry point (src/index.ts, lines 1-15) → High-level: This is where your app boots. We wire up the database and start the server here. STEP 2-4: Database setup (prisma/schema.prisma) → Our three core tables: User, Subscription, CreatorProfile → Focus: Many-to-one relationship between Creator and Subscription (lines 47-61) STEP 5-7: Auth middleware (src/middleware/auth.ts) → JWT validation, session refresh, role checking → Common gotcha: expired tokens don't error, they silently fail (line 34) STEP 8-10: API routes (src/api/subscriptions.ts) → POST /subscriptions (create new sub), GET /:id (fetch), DELETE (cleanup) → Pattern: always validate user ownership before mutating (line 52) STEP 11-15: Error handling and logging → Where logs go, how to trace a request through the system → Debug tip: check src/utils/logger.ts for context field ordering ESTIMATED VIEWING TIME: 8 minutes
About this skill
name: code-tour description: Use when Use when the user asks to create a CodeTour .tour file — persona-targeted, step-by-step walkthroughs that link to real files and line numbers.
Code Tour
Use when the user asks to create a CodeTour .tour file — persona-targeted, step-by-step walkthroughs that link to real files and line numbers. Trigger for: create a tour, onboarding tour, architecture tour, PR review tour, explain how X works, vibe check, RCA tour, contributor guide, or any structured code walkthrough request.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the code-tour skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Code Tour; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: code-tour
description: Use this skill when the user asks to create a CodeTour file, a persona-targeted, step-by-step walkthrough that links to real files and line numbers.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Code Tour
Builds a structured code walkthrough that steps through real files and line numbers, tailored to who the tour is for.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.