code-tour

You can create a codebase walkthrough by generating standardized CodeTour files with verified file and line anchors. This replaces ad-hoc explanations by producing interactive, in-IDE tours calibrated specifically for new joiners.

Documenting root cause analysis is best done by generating CodeTour files that anchor directly to the relevant code paths and line numbers. This creates reusable, verifiable walkthroughs for RCA investigators instead of disposable notes.

Yes, you can generate a pull request review walkthrough using CodeTour files. The skill validates all referenced file paths and line numbers against the target repository to ensure PR reviewers see accurate, interactive anchors.

You can build an architecture tour by requesting a persona-adapted CodeTour for architects. The skill generates a multi-step walkthrough that deep dives into specific code modules while calibrating the depth for the intended reader.

Yes, generated code tours validate all referenced file paths, directory anchors, and line numbers against the target repository. This strict adherence to the CodeTour JSON schema ensures interactive walkthroughs do not contain broken links.

You should avoid ad-hoc codebase explanations during onboarding, PR reviews, and RCA when you need reusable documentation. CodeTour files replace one-off explanations with standardized, persona-calibrated walkthroughs that save engineering time.