Every pull request worth explaining, explained.

Claude Code reads each pull request as it opens. When the change deserves more than a diff, your reviewers find a short video of what changed and why, right in the thread.

Paste it into Claude Code in your repository. Free on your Claude plan. Set it up by hand

Enforce max-turn limits from claude_args #1607

Mergedanthropics/claude-code-action Β· 4 files
github-actionsbotcommented

Fix a typo in the install command

Openyour-org/app Β· 1 file
github-actionsbotcommented

No explainer for this pull request. It only corrects one word in the README.

Set up once. Every pull request after that is covered.

  1. Step 1

    Paste one line into Claude Code

    It adds the workflow to your repository. You make the one token yourself, because only you can sign in to your Claude account.

    claude setup-token
  2. Step 2

    Open pull requests the way you already do

    Claude Code reads each one as it opens and decides whether it is worth explaining to someone who did not write it.

    pull_request: opened
  3. Step 3

    Reviewers press play

    A design decision or a migration gets a walkthrough in the thread. A typo fix gets one line saying why it was skipped.

    Watch the explainer

Want one Claude Code skipped? Ask.

Comment @bisque-cloud on any pull request and it makes the explainer, whatever it decided before. Anyone with write access can ask.

you commented

@bisque-cloud this one touches billing, walk us through it

1eyes reaction

Releases get one too.

When you publish a release on GitHub, Claude Code makes a walkthrough of what is new since the last release and links it in the release notes.

Your Claude plan, or your own API key
Each explainer is one Claude Code run on the subscription you already pay for. An API key from Google, OpenAI, xAI or Anthropic works too.
Private repositories stay private
Only people who can open the repository on GitHub can watch. Access is rechecked every 12 hours.

Questions

What does it cost?
Claude Code runs on your Claude plan. Publishing and hosting are free. GitHub Actions is free on public repositories; a private one uses a few minutes per explainer.
Which pull requests get one?
The ones a reviewer would want walked through, like a design decision, a new command or a migration. A typo fix gets a one-line comment saying why it was skipped.
How long does it take?
The link arrives as a comment several minutes after the pull request opens.
Where do the explainers live?
On your repository's channel, bisque.today/p/owner/repo. A new explainer for the same pull request replaces the old one.

Your next pull request could arrive with its own walkthrough.

Read the setup guide