docs: update Claude Code documentation

Author: github-actions[bot]

README.md

@@ -28,7 +28,7 @@
 
 ---
 
-> **Last docs pull:** <!-- LAST_UPDATED -->2026-07-02 21:14 UTC / 14:14 PT / 17:14 ET / 23:14 CET / 02:44+1 IST / 06:14+1 JST<!-- /LAST_UPDATED -->
+> **Last docs pull:** <!-- LAST_UPDATED -->2026-07-02 23:12 UTC / 16:12 PT / 19:12 ET / 01:12 CET / 04:42+1 IST / 08:12+1 JST<!-- /LAST_UPDATED -->
 
 A GitHub Actions workflow runs every hour, downloads the latest docs, and commits any changes automatically.
 

claude-code-docs/workflows.md

@@ -180,6 +180,81 @@ The following prompt runs a saved workflow with a list of issue numbers:
 
 Claude passes the list as structured data, so the script can call array and object methods on `args` directly without parsing it first. If `args` is omitted, the global is `undefined` inside the script.
 
+## Example workflow prompts
+
+A workflow fits best when the task is larger than one agent can hold in context, or when the same step needs to run across many items. The prompts below show common shapes. Each one asks Claude to write and run a workflow for that task; you don't write the script yourself.
+
+### Audit many files for the same issue
+
+Fan out one agent per file, then collect and verify the findings.
+
+```text
+> use a workflow to audit every route handler under src/routes/ for missing authentication checks, and adversarially verify each finding before reporting it
+```
+
+### Keep fixing until a check passes
+
+Run a checker, fix what failed, and repeat until it passes or stops making progress.
+
+```text
+> use a workflow to run npx tsc --noEmit and keep fixing the reported errors until the type check passes or two rounds in a row make no progress
+```
+
+### Migrate many files in parallel
+
+Discover the files to migrate, transform each one in an isolated copy so edits don't conflict, and verify each result.
+
+```text
+> use a workflow to migrate every component under src/components/ from styled-components to Tailwind, working on each file in its own isolated copy
+```
+
+### Review every changed file and write one summary
+
+Run a reviewer per file, then hand all the findings to one agent that ranks and deduplicates them.
+
+```text
+> use a workflow to review every file changed in this PR for correctness issues, then merge the per-file findings into one ranked summary
+```
+
+### Research a topic across many sources
+
+Fan out readers across changelogs, issues, and docs, then synthesize. The bundled `/deep-research` workflow does this; you can also describe a narrower version.
+
+```text
+> use a workflow to research how our three competitors handle rate limiting: read their public docs and recent changelog entries in parallel, then compare the approaches
+```
+
+### Find issues until the list stops growing
+
+Keep searching in rounds and stop when new rounds turn up nothing new.
+
+```text
+> use a workflow to find flaky tests in this repo: run the suite repeatedly, record which tests fail intermittently, and stop once two rounds in a row find nothing new
+```
+
+### What the saved script looks like
+
+When you [save a workflow](#save-the-workflow-for-reuse), the file in `.claude/workflows/` holds a `meta` block followed by a script body that orchestrates subagents. You usually don't need to edit it, but here is the shape of a small one so you can recognize what Claude generated:
+
+```javascript
+export const meta = {
+  name: 'audit-routes',
+  description: 'Audit every route handler for missing auth checks',
+}
+
+const found = await agent('List every .ts file under src/routes/.', {
+  schema: { type: 'object', required: ['files'], properties: { files: { type: 'array', items: { type: 'string' } } } },
+})
+
+const audits = await pipeline(found.files, file =>
+  agent(`Audit ${file} for missing authentication checks.`, { label: file }),
+)
+
+return audits.filter(Boolean)
+```
+
+The body is plain JavaScript with top-level `await`. `agent()` spawns one subagent and `pipeline()` runs one per item in a list. If you want to edit a script by hand, ask Claude to walk you through the change, or see the Workflow tool entry in the [Agent SDK reference](/en/agent-sdk/typescript) for the full set of options.
+
 ## How a workflow runs
 
 The workflow runtime executes the script in an isolated environment, separate from your conversation. Intermediate results stay in script variables instead of landing in Claude's context.