Add a FAQ section with three questions
- Plan in the description done
- Design check 0 problems
- Screenshots, desktop and phone attached
- Your review required
00 — the outcome
Comment @claude on a GitHub issue. A few minutes later there is a pull request with a plan, passing checks and screenshots, waiting for your review.
01 — how it works
Plain words, with @claude in it: "add a FAQ section".
In GitHub Actions. It reads CLAUDE.md, DESIGN.md and its skill before it touches a file.
With the plan, the design check result and before and after screenshots.
Review, ask for changes with another @claude, or merge. Merging publishes the site.
02 — guardrails
GitHub's short-lived OIDC token is swapped for a 10-minute Claude token. No secret in the repo.
One federation rule: this repository, the main branch, comment and issue events only.
A monthly spend limit on its own workspace, 40 turns and 20 minutes per run.
Edits to .github/, .claude/ and CLAUDE.md are denied in its settings.
A ruleset on main requires a human review and a passing design check.
03 — faq
A monthly spend limit of US$20 on its own workspace. Each run stops after 40 turns or 20 minutes.
It can't merge, approve or push to main. It can't change its own rules in .github/, .claude/ or CLAUDE.md.
Cancel the run in the Actions tab. To stop every run, disable the workflow there. To revoke its access, remove the Claude GitHub App from the repository.
04 — try it
@claude add a FAQ section with three questions a team lead would ask@claude add a dark mode that follows the system setting@claude make the guardrails section easier to scan on a phoneMaintainers and people on the allowlist start the agent. Anyone else's request waits for a maintainer to approve it. Use the kit in your own repository to try it yourself.