Tag @bisque-cloud on a pull request and Claude Code makes an explainer video

1 day ago

@siderakisSubscribe

Mention @bisque-cloud in a comment on a GitHub pull request, and Claude Code makes an explainer video of it, free within your Claude subscription. It lands on your repository's own channel. The opening explainer is an example, made with the present skill for anthropics/claude-code-action pull request 1607 before the mention existed. Setup page: https://bisque.today/docs/github Example pull request: https://github.com/anthropics/claude-code-action/pull/1607 Its explainer: https://bisque.today/p/siderakis/max-turns-from-claude_args-now-stops-the-run https://github.com/bisque-cloud/presenter

Ask

Ask about this presentation

Answers are generated from this presentation.

Chapters

  1. 0:00A PR explainer video, from one comment
  2. 0:20An example: claude-code-action #1607, explained
  3. 0:48Ask for one in a pull request comment
  4. 1:11From a comment to a watch link
  5. 1:29Every explainer lands on your repository's own channel
  6. 1:51Setup: hand your agent the setup page
  7. 2:06Before you turn it on
  8. 2:34Which pull request would you explain first?
Show transcript

A PR explainer video, from one comment

Claude CodeYour Claude planBisque Presenter
Explainer for anthropics/claude-code-action#1607 ↗
What you getHow it worksSetup

This is a pull request explainer, and Opus 5.5 made all of it: the slides, the narration and the motion design, from the diff. Mention @bisque-cloud in a comment on a GitHub pull request, and Claude Code makes one like it, free within the Claude subscription you already have.

An example: claude-code-action #1607, explained

Example · made with the present skill, before the @bisque-cloud mention
anthropics/claude-code-action pull request 1607: Enforce max-turn limits from claude_args

github.com/anthropics/claude-code-action/pull/1607

What you getHow it worksSetup

This example is for a public pull request in Anthropic's claude-code-action. A run capped at sixty turns ran seventy-three and still passed, and this change makes the cap hold. The explainer walks through the fix, then ends on what a reviewer should check, including one the pull request doesn't mention: writing the cap as the word sixty turns it off. It was made with the same present skill the mention runs, before the mention existed.

Ask for one in a pull request comment

A pull request on siderakis/release-explainer-oidc-check with the comment @bisque-cloud explain this and an eyes reaction
👀 says the run startedWithin a minute of the comment.
A reply links the explainerA few minutes later, once it is published.
Only people with write access can askAnyone else's mention starts nothing.
A real mention on a public test repository. It has no Claude token, so it got the 👀 and no reply. ↗
What you getHow it worksSetup

Here's a real request, on a public test repository: a comment that says @bisque-cloud explain this. The eyes mean the run started. Once the repository has your Claude token, a reply links the explainer a few minutes later. This test repository has none, so it stopped at the eyes. And only people with write access can start one.

From a comment to a watch link

@bisque-clouda comment on the pull request
GitHub Actionsruns the workflow in your repository
Claude Codereads the change, on your Claude plan
present skillwrites slides, narration, motion
bisque-voicespeaks it on the runner
Watch linkposted as a reply
What you getHow it worksSetup

Here's the path. The mention starts a GitHub Actions workflow in your repository. Claude Code reads the change, on the plan you already pay for, the present skill writes the slides and narration, bisque-voice speaks it on the runner, and the link comes back as a reply.

Every explainer lands on your repository's own channel

Every explainer lands on your repository's channel

The repository's channel on bisque.today, siderakis/release-explainer-oidc-check, with a Claim with GitHub button and the explainer its workflow published
No Bisque account to makeThe workflow publishes with its own GitHub sign-in.
bisque.today/p/{owner}/{repo}The same path as on GitHub.
Public repository, public explainersA private repository's are unlisted.
The test repository's channel, bisque.today/p/siderakis/release-explainer-oidc-check ↗
What you getHow it worksSetup

The workflow publishes with its own GitHub sign-in, so there's no Bisque account to make. Every explainer lands on your repository's own channel, under the same owner and repository path as on GitHub. This is the test repository's. A public repository's explainers are public, and a private one's are unlisted.

Setup: hand your agent the setup page

The setup page at bisque.today/docs/github, down to the line to hand your agent
Tell your agentSet up the Bisque pull request explainer on this repository by following https://bisque.today/docs/github.md
Your part: sign in to ClaudeThe agent asks you to run claude setup-token, so every run uses your plan.
What you getHow it worksSetup

To set it up, hand your coding agent the GitHub setup page on bisque.today, and it adds the workflow. The part it leaves to you is signing in to Claude, so Claude Code runs free within the subscription you already have.

Before you turn it on

Several minutes eachAnd each run counts toward your Claude usage limits.
Only on requestYour plan is spent only when someone with write access asks.
Strangers' pull requests: add network: denyThe agent then reads their text with no shell and no internet.
What you getHow it worksSetup

Before you turn it on. An explainer takes several minutes, and each one counts toward your plan's usage limits, like anything else you run in Claude Code. It runs only when someone with write access mentions it, so your plan is spent only when someone you trust asks. And if your repository takes pull requests from strangers, add network deny to the workflow. The agent then reads their text with no shell and no internet.

Which pull request would you explain first?

Which pull request would you want explained first?

The bisque-cloud/presenter repository on GitHub
bisque.today/docs/githubgithub.com/bisque-cloud/presenterHand the setup page to your agent

Hand your agent the setup page, mention @bisque-cloud on a pull request, and your reviewers get a video they can watch before reading the diff. Which pull request would you want explained first?