Rails PR Tour

Code review tools list files alphabetically. For a 40-file PR that is the wrong order: reviewers report more context switching and missed bugs, and what they ask for instead is dependency order and grouping by purpose (Rahman et al., ICSE 2026). Rails makes both cheap: the layer is in the path, and the dependencies are in the constants.

This skill produces a tour: chapters of related files in the order a reviewer should read them, with a reason per file and a risk marker where the reviewer should slow down. It is a map, not a review. A review skill (/code-review, jr-rails-second-opinion, or your own) does the reviewing; this skill tells you where to look first.

Read @references/guide.md and follow it. Do not proceed without it. Host commands and deep-link anchors are in @references/hosts.md. The artifact page is @references/tour-template.html; fill its data block, do not rewrite the page.