Installs into .claude/skills of the current project.
Are you the author of Redline Tour?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/nikiforovall-redline-tour)
---
name: redline-tour
description: Open the current diff as a Redline review round in VS Code with a numbered walkthrough attached, then listen for the review.
disable-model-invocation: true
---
# redline-tour
Post one round with a guided tour, then invoke the `redline:redline-connect` skill.
Read `${CLAUDE_PLUGIN_ROOT}/reference/ROUND.md` first: it resolves the source from `$ARGUMENTS`, sets the title, and carries the `request_review` call and its stop rules. Read `${CLAUDE_PLUGIN_ROOT}/reference/NOTES.md` before writing the first note.
## Write the tour
Read the diff for the chosen source before writing anything.
A tour note is a guide's caption: it tells the reader what the hunk does and why the change needs it, in the voice of the author walking someone through their own work. Every note in `notes` is a numbered stop on the tour; the numbered sequence is the complete list. Anything else you noticed while reading the diff, such as a bug, a risk, an open question, or a better approach, goes in your chat reply under a "Noticed" line after the round report, where the user decides what to do with it.
1. Decide the reading order. Start where the change begins for a reader: the entry point, the type or contract that everything else depends on, then callers, then tests. Not file order, not diff order.
2. Pick the stops. A stop is one idea. It sits on the hunk where that idea lives, and its body names the other files that only carry the idea. Most changes have three to five ideas. A stop count near the file count means the tour walks files. Before posting, remove every stop a reader could skip and still follow the change. Renames, imports, formatting, type plumbing, and doc updates go first.
3. Number every note with a bold bracketed prefix on the first line of its `body`: `**[<n>/<total>]** `. The reader follows the numbers through the Comments panel.
Example for a three-note tour:
```
**[1/3]** Adds the `Quote` type the parser and printer both read.
**[2/3]** Parser emits `Quote` for lines that start with a marker.
**[3/3]** Printer renders `Quote` as an indented block.
```
When you report the round, add the note count to the line.
