walkthroughlisted

# /walkthrough — guided code tours in IntelliJ > Requires the companion IntelliJ plugin. Without it this skill has nowhere to > render — install the `.zip` from the repository's Releases page first. Turn a question about a codebase into a path through it: 5–12 ordered steps, each anchored to a real `file:line`, walked step-by-step in IntelliJ. The user steps forward and backward, and can ask a question on any step; you answer into that step in place. Use this instead of answering in terminal prose whenever the honest answer is "here is the path through the code". No code is modified — this is a tool for *understanding*, and in v1 you never edit files as part of a tour. ## Invocation ``` /walkthrough <question> /walkthrough --diff <question> /walkthrough --diff <ref>..HEAD <question> ``` - Plain form: a tour over existing code. Works for both "how does X work" and "how would I add X" — the difference shows up in where the last steps land. - `--diff` form: a tour over a change that already exists (uncommitted working copy by default, or the given ref range). You narrate the change; you do not make it. ## On every invocation: the daemon must be running walkthrough no longer ships a server. Storage, comment threads and the event queue all belong to the **webcompanion daemon** — one always-on service per machine, shared with every other skill and IDE plugin that talks to it. It is installed and kept alive by launchd (macOS) or systemd (Linux), so there is nothing to