/hyperpower:walkthrough

With no argument it shows where things stand:

Walkthroughs are on in hyperpower.yml.
Runner 0.1.0 installed at ~/.claude/hyperpowers-runner/0.1.0.

Journeys in journeys/:
  _login               2 steps, lock fresh
  email-notifications  5 steps, lock fresh

explain is for reviewing someone else's pull request, whoever wrote it:

Explained #1: 8 files, 12 changed blocks.
Open it in VS Code: click the Hyperpowers icon in the activity bar; Explained Pull Requests lists it.

It saves what the change does, what each file is for, and what each changed block does and why, in your own checkout. Nothing is posted anywhere. The Hyperpowers Walkthrough extension for VS Code lists it and walks you through the code.

When the change was built with Claude Code on your machine, explain reads what was asked while each file was edited, with passwords and keys removed, and uses it for the why. For a file nothing else explains, it uses the brief a subagent got before it edited that file. It prints how many sessions it used. --no-sessions leaves them out, and so does walkthrough: { use_claude_sessions: false } in hyperpower.yml.

share writes one .walkthrough file to send to a reviewer. With no argument it takes your latest run's recordings; with a pull request number, that pull request as explained here:

Wrote .hyperpower/shares/app-pr-12.walkthrough (1.4 MB): 1 journey, 8 changed files.
It holds the code of every changed file and any screenshots. Send it only to people who may see them.

The reviewer opens it in VS Code with Walkthrough: Open Walkthrough File. They need neither the repository nor hyperpower.

record replays the journeys this branch changed and records them, outside a full run. publish pushes the recordings to a hyperpower/walkthroughs branch on the same remote as your code. Reviewers open them from VS Code and see each step's screen beside the code behind it.

install fetches the runner, about 10 MB. It uses the Chrome you have and downloads no browser.