一键导入
release-notes
Draft short release notes from a list of changes. Use when the user asks for changelogs, release notes, or a concise product update.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Draft short release notes from a list of changes. Use when the user asks for changelogs, release notes, or a concise product update.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | release-notes |
| description | Draft short release notes from a list of changes. Use when the user asks for changelogs, release notes, or a concise product update. |
Turn implementation details into user-facing release notes.
When the user provides a rough list of changes, run
scripts/format-release-notes.ts with { "changes": [...] } to create a first
draft, then polish the wording for the user's audience. The TypeScript script
is function-style (export default run(input, ctx)) and demonstrates reading
references/style-guide.md from ctx.files.
Use this structure:
## Summary
- One to three bullets describing what changed.
## Notes
- Optional caveats, migration details, or follow-up work.
If the input is too vague, ask for the target audience and the release scope.
Take a cloudflare/agents GitHub issue plus any repro findings and one-shot a fix PR — branch, change, test, push, and open the PR linked to the issue.
Reproduce a cloudflare/agents GitHub issue by scaffolding a minimal Agents/Worker project and deploying it to a temporary Cloudflare account, then report findings back on the issue.
Review code changes for correctness, clarity, and risk. Use when the user asks for a review, a second opinion on a diff, or feedback on code they wrote.
Decide when and how to escalate a customer conversation to a human agent. Use when a request is high-risk, the customer is frustrated, or the issue is outside what you can resolve.
Summarize the files saved in this assistant's shared workspace. Use when the user asks what is in their workspace, for a file inventory, or a digest of saved work.
Create a systematic debugging plan for a bug report. Use when the user asks how to investigate a failure, regression, or unexpected behavior.