菜单
Use when writing a pull request title or body, when about to run gh pr create, when about to git push on a branch that already has an open PR, or when the user says /pr-description, "write the PR description", or "update the PR title". Don't use for commit messages, changelogs, or review comments.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/TanStack/ai --skill pr-description命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Entry point for TanStack AI skills. Routes to chat-experience, tool-calling, media-generation, structured-outputs, adapter-configuration, ag-ui-protocol, middleware, locks, custom-backend-integration, and debug-logging, plus the skills shipped by companion packages (@tanstack/ai-persistence, @tanstack/ai-code-mode). Use chat() not streamText(), openaiText() not createOpenAI(), toServerSentEventsResponse() not manual SSE, middleware hooks not onEnd callbacks.
Portable Agent Skills (SKILL.md) for TanStack AI with @tanstack/ai-skills. Renders a skill catalog and a load_skill tool via the withSkills middleware so any tool-calling model loads skills on demand, on any provider. Covers the SkillSource interface, inlineSkill/skillDirectory/staticSkills, the aggregate/ dedupe/filter/cache combinators, read_skill_resource, and the conformance suite. Use for provider-agnostic runtime skills — NOT hosted provider skills (codeExecutionTool/shellTool), which run in a provider sandbox.
does the alpha thing
正在显示 SKILL.md
| name | pr-description |
| description | Use when writing a pull request title or body, when about to run gh pr create, when about to git push on a branch that already has an open PR, or when the user says /pr-description, "write the PR description", or "update the PR title". Don't use for commit messages, changelogs, or review comments. |
Write the GitHub PR title and body, then post them. Do not wait for approval.
Work from the diff, not from memory.
This skill is auto plus on demand.
Run it:
/pr-description.gh pr create.git push on a branch that already has an open PR. Then run gh pr edit with a fresh title and body.Do not run it on a human-only git push in another terminal. Do not add a git hook.
A later push must rewrite the GitHub text. Do not leave a stale description.
A fix PR must pass bugfix-pr first. If those gates fail, stop. Do not run gh pr create. Do not run gh pr edit.
simple-english and i-have-adhd are prerequisites. They apply to the PR title and body, not to the rest of the session.
Load both immediately before writing the title and body. Use the Skill tool if this harness has one. If it does not, Read:
.claude/skills/simple-english/SKILL.md.claude/skills/i-have-adhd/SKILL.mdCopies also live at .agents/skills/ (Codex) and .grok/skills/ (Grok). Keep those three files identical.
If either file is missing, stop. Do not post a weaker substitute.
When i-have-adhd is loaded from this skill, ignore its persistence section. Do not switch the rest of the session into ADHD mode.
Use pragmatic simple-english. Then shape the text with i-have-adhd: next action first in the lead, numbered steps for manual test, lists capped at 5.
main / master / develop).git log --oneline base...HEAD and git diff base...HEAD..github/pull_request_template.md if it exists (also check .github/PULL_REQUEST_TEMPLATE.md and .github/PULL_REQUEST_TEMPLATE/).gh pr list --limit 15 --state all --json title). Match that shape. Do not invent a new title style.Closes # / Fixes # text.Pick one kind from the diff:
| Kind | Signal |
|---|---|
| fix | Restores broken behavior. A user-visible bug, a failing test, a regression. |
| feat | Adds behavior that did not exist. New export, new command, new user-facing flow. |
| chore / docs | Agent files, CI, docs-only, refactors with no user-visible behavior change. |
If both a feat and a fix are in the diff, the larger user-visible story wins. Say so in the lead.
If none of those exist, stop. Do not run gh pr create. Do not run gh pr edit. Tell the user what is missing. Wait until they add one, then continue.
A fix does not use this gate. A fix uses bugfix-pr. Load it first.
A chore / docs PR does not use this gate.
Match this repo's recent PR titles. In a conventional-commit repo, write type(scope): summary. Keep it one line.
The title must still make sense if the reviewer never opens the body.
Load simple-english and i-have-adhd, then write in this order.
Lead (required, 1 to 4 sentences, before the template).
No preamble. No "This PR aims to". Start with the fact.
Repo template (required when the file exists).
Fill every section honestly. Leave a checkbox unchecked when the claim is false. Do not tick "I ran pnpm test:pr" if you did not run it.
Extra sections after the template, in this order. Testing and Risk / rollback are always present. For a fix, Root cause and Possible alternatives are also always present. Linked issues and Public API change are omitted when they do not apply.
Required for a fix. Copy from the bugfix-pr report. Do not paste
the diff. Write:
## Root cause
**Issue.** What is broken, for whom, under which inputs.
**Cause.** Why it happens in the code. Name the function or path.
**Fix.** How this PR's change kills that cause.
Required for a fix. Copy from the bugfix-pr report. Write:
## Possible alternatives
- **<name>.** What it is. Why this PR did not take it.
If there is no other real way, write None. Do not omit the heading.
Three parts, all required:
Omit this heading when nothing links. When an issue links, use Closes #N or Fixes #N.
What could break. How to undo (revert the PR, turn a flag off, and so on). If risk is low, say that in one line. Do not skip the heading.
Omit this heading when the PR does not touch the published surface.
Published surface means: exported functions, types, components, CLI flags, env vars, and documented contracts from published packages. Tests, internal files, agent skills, AGENTS.md, and CLAUDE.md do not count.
When it does touch that surface, show caller usage, not the internal diff:
## Public API change
**Before**
\`\`\`ts
old call site
\`\`\`
**After**
\`\`\`ts
new call site
\`\`\`
Two short snippets. What a user writes today, then what they write after this PR.
Do not wait for the user to approve the text.
gh pr create --title "..." --body-file ...gh pr edit --title "..." --body-file ...If gh fails, stop and show the error. Leave the drafted body in the chat so it is not lost.
Do not attach screenshots to the PR. Do not commit screenshot files for this skill.
| You catch yourself | Do instead |
|---|---|
| Writing the body from the branch name | Read the diff. |
| Ticking a template checkbox you did not do | Leave it unchecked and say so in Testing. |
| Posting a feat with no test, command, or example | Stop. The feat gate failed. |
| A 1-4 sentence lead that lists files | Rewrite as what a user can do, or what bug is gone. |
| Public API section that shows the internal diff | Show caller usage before and after. |
| Public API section on an AGENTS.md-only PR | Omit the heading. |
| "I'll update the description later" after a push | Rewrite now with gh pr edit. |
| Waiting for the user to approve the text | Post. This skill does not wait. |
| Uploading or committing screenshots for the PR body | Skip. Do not put images on the PR. |
| Writing without loading simple-english and i-have-adhd | Load both from the repo copies. If missing, stop. |
Posting a fix before bugfix-pr gates pass | Stop. Load bugfix-pr. Do not create or edit. |
| A fix PR with no Root cause or Possible alternatives | Copy both sections from the bugfix-pr report. |