> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pullstory.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a code walkthrough with Claude Code

> End-to-end MCP workflow from source files to narrated pull story.

## The workflow

You've written some code and want a narrated video walkthrough. With the pull/story MCP server installed, this is one sentence to Claude Code.

<Steps>
  <Step title="Make sure the MCP is installed">
    See the [Claude Code setup guide](/integrations/claude-code) if you haven't yet.
  </Step>

  <Step title="In Claude Code, type">
    ```
        Make a pull story explaining the payment retry flow
    ```
  </Step>

  <Step title="Claude Code will">
    1. Identify the files that matter
    2. Read tight line ranges from those files
    3. Extract the runtime flow and important gotchas
    4. Call the pull/story MCP tool `create_pull_story` with a structured brief
    5. Poll `get_pull_story` until ready
    6. Paste the URL back into the chat
  </Step>

  <Step title="You get">
    A clickable pull story URL in the chat, ready to share with reviewers or embed in Slack.
  </Step>
</Steps>

## Example conversation

> **You:** Make a pull story explaining the payment retry flow.
>
> **Claude Code:**
> I'll inspect the payment retry code path and build a concise brief.
>
> \[reads `src/payments/retry.ts`, `src/jobs/payment-retry-worker.ts`, and `src/lib/billing.ts`]
>
> Generating pull story…
>
> \[calls `create_pull_story({title, summary, repo, files, flow, highlights})`]
>
> Generating… this usually takes about 90 seconds. Polling…
>
> Pull story ready: **[https://pullstory.com/s/brief\_0123abcd4567ef89](https://pullstory.com/s/brief_0123abcd4567ef89)**
>
> Duration: 2m 18s · 7 scenes

## Variations

<AccordionGroup>
  <Accordion title="Explain a specific area">
    > **You:** Walk me through how login sessions work
    >
    > Claude Code finds the relevant auth files, reads them, then calls `create_pull_story`.
  </Accordion>

  <Accordion title="Regenerate an existing story">
    > **You:** Make that pull story again but focus only on retry backoff
    >
    > Claude Code builds a narrower brief and calls `create_pull_story` again.
  </Accordion>
</AccordionGroup>

## Why this beats copy-pasting diffs

Traditional flow: paste snippets into chat → explain architecture from memory → answer 3 rounds of clarifying questions.

Pull/story flow: say one sentence → get a video link grounded in real files. Teammates watch 2 minutes and actually understand the system before leaving feedback.

## Next

<CardGroup cols={2}>
  <Card title="GitHub App auto-gen" icon="github" href="/integrations/github-app">
    Install once — skip the "ask Claude Code" step entirely.
  </Card>

  <Card title="Embed pull stories" icon="code" href="/cookbooks/embed-a-pull-story">
    Drop a pull story inline in docs, changelogs, blog posts.
  </Card>
</CardGroup>