菜单
Generate a commit message or PR description for ReactUse in the repo's conventional-commit style, derived from the actual git diff. Triggers on "write the PR description", "draft a commit message", "describe this change", or before opening a PR.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
把博客文章发布到 Medium（@wul55267），通过 opencli 浏览器自动化。Medium 编辑器是富文本，不吃裸 markdown，所以用 pandoc 把正文转 HTML，再模拟一次 paste 事件灌进去。当用户说"发到 medium"、"推送 medium"、"publish to medium"、"cross-post to medium"，或在写完/commit 了一篇新博客后说"发出去"、"同步发布"、"把这篇发了"时触发；也用于多平台分发流程（dev.to + Medium + Hashnode + 掘金）里的一环。
把博客文章发布到掘金（juejin.cn），通过 opencli 浏览器自动化。掘金编辑器是 ByteMD（CodeMirror 内核的 markdown 编辑器），直接吃 markdown，比 Medium 好搞。发的是简体中文版（juejin.md）。当用户说"发到掘金"、"推送掘金"、"publish to juejin"、"把这篇发掘金"，或在写完/commit 了一篇新博客后说"发出去"、"同步发布"、"推平台"时触发；也用于多平台分发流程的一环。
Write the Astro .mdx documentation for a hook (English + zh-Hans + zh-Hant), following the website-astro content schema and live-demo convention, then regenerate scripts/hook-registry.json. Triggers on "document this hook", "add docs for useXxx", "write the mdx", or after creating a new hook.
Write and run jest tests for a hook in @reactuses/core, following the repo's conventions (co-located index.spec.ts, renderHook/act, fake timers, the .test/ helpers, and the SSR jest-environment pragma). Triggers on "write a test", "add test coverage", "fix the failing test", or "test this hook".
Scaffold a new React hook in @reactuses/core with the repo's real conventions (interface.ts + multilingual JSDoc, SSR-safe browser access, shared-util reuse, 3-part public export). Triggers on "add a hook", "new hook", "scaffold a hook", "create a useXxx", or when implementing a new piece of hook functionality in packages/core.
把博客文章发布到 Hashnode (reactuse.hashnode.dev)，canonical URL 指回 reactuse.com。默认走 opencli 浏览器自动化（GraphQL API 已转付费）。当用户说"发到 hashnode"、"推送 hashnode"、"cross-post to hashnode"、"publish to hashnode"，或在写完/commit 了一篇新博客后说"发出去"、"同步发布"、"把这篇发了"、"publish the latest post"时触发。也在 `/publish` 类的工作流里作为多平台分发的一环。
| name | pr-description |
| category | engineering |
| description | Generate a commit message or PR description for ReactUse in the repo's conventional-commit style, derived from the actual git diff. Triggers on "write the PR description", "draft a commit message", "describe this change", or before opening a PR. |
Generate a title + body from the real diff, matching this repo's conventions. Don't invent scope or impact — read what actually changed.
git status
git diff --stat
git diff # or: git diff origin/main...HEAD for a branch
git log --oneline -10 # match the prevailing style
Format: type(scope): summary — imperative, lowercase, no trailing period.
Types seen in this repo: feat, fix, docs, chore, refactor, test.
Common scopes: core (hooks), website, blog, readme, mcp, skill.
Real examples from history:
feat(core): add useMicrophone hook (#198)fix(core): emit default values in generated API docsdocs(website): add useMicrophone hook documentation (#199)docs(blog): add React event hooks post (en, zh-Hans, zh-Hant)chore: release v6.3.3Pick the type by the dominant change. A new hook is feat(core):; its docs are
docs(website):; they're usually separate commits/PRs.
Keep it tight. Include only sections that apply:
## What
- bullet of each meaningful change
## Why
- the motivation / problem solved
## Test plan
- pnpm --filter @reactuses/core test useX
- pnpm lint
- (for docs) built locally / live demo renders
## AI assistance
- e.g. scaffolded with the new-hook skill (optional, see .claude/ai-policy.md)
scripts/hook-registry.json — never invent a
hook name, category, or URL. Links must be the lowercase canonical form.(en, zh-Hans, zh-Hant)).ai-policy.md), not required.