Pull requests in VS Code

Say yes to walkthroughs in /hyperpower:init. From then on, every change you can see in the app gets a short journey: a few plain sentences about what a person does, and what should be true after each one. The run replays it in Chrome and records every step, with the lines of code behind it.

When the pull request is open, /hyperpower:walkthrough publish pushes the recordings to your own git remote. Nothing is posted to the pull request.

Reviewing someone else's pull request

This part works on any pull request, built with hyperpower or not, and needs only the Hyperpowers extension for VS Code. Open the repository in VS Code, click the Hyperpowers icon in the activity bar, then click + (Create Walkthrough) at the top of Code Reviews and paste the pull request's link or number. Your Claude Code explains it, with progress as it goes.

From Claude Code, the plugin does the same. In your checkout:

/hyperpower:walkthrough explain 1

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

Either way, it saves what the change does, what each changed file is for, and what each changed block does and why. The pull request appears under Code Reviews. Press Start the review and it opens each change beside its explanation, in the order the code runs. The notes say they were written by a model reading the diff, so check them against the code.

The extension keeps your place: files you have read are ticked, and reopening offers Continue the review. When commits are pushed after you explained the pull request, a line at the top of the review says how many, and Update explains only the files they changed.

To send a review to someone else, click … on it under Code Reviews and choose Export walkthrough, or run /hyperpower:walkthrough share 1. Either writes one .walkthrough file. Drop it in Slack. They click Load Walkthrough File in the Hyperpowers panel, and they don't need Claude Code to read it.