菜单
Prepare GitHub issues, pull requests, reviews, and release notes for Zhin projects. Use when asked to write an issue, PR description, changelog entry, or review comment. Triggers: 写 issue, PR 描述, 提 PR, release notes, gh pr.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Implement Zhin.js plugins with the standard development workflow. Use when asked to create a plugin, add commands, middleware, event hooks, components, cron jobs, Contexts, AI tools, AI skills, AI agent presets, config schema, database, router, or web console integration, or follow the recommended Zhin plugin development pattern. 适用于 Zhin 插件标准开发姿势实现、插件功能落地、命令与 Context 接入。
初始化 Zhin.js 插件项目。Use when asked to create a new plugin, scaffold plugin structure, or set up a plugin project. 引导生成符合 Zhin 规范的目录结构、package.json、tsconfig、入口文件和 README。
Audit Zhin.js monorepo for security vulnerabilities, performance bottlenecks, and architecture issues. Use when asked to "audit code", "check security", "find performance issues", "review architecture", "scan for vulnerabilities", "check memory leaks", or "review code quality".
Implement Zhin.js plugin features: commands, AI tools, cron jobs, middleware, and console pages. Use when asked to add a command, register a tool, wire cron, extend middleware, or build a console page entry. Triggers: 插件开发, add command, addTool, 加命令, 写插件功能.
Refactor existing Zhin.js plugins into a cleaner standard structure. Use when asked to reorganize plugin files, split commands or services, migrate a messy plugin to standard layout, reduce coupling, clean lifecycle logic, or standardize plugin structure without changing behavior. 适用于已有 Zhin 插件重构、结构整理、职责拆分与标准化迁移。
发布 Zhin.js 插件到 npm 和 Zhin 插件市场。Use when asked to publish a plugin, prepare for release, check publish readiness, or submit to the Zhin plugin marketplace. 引导完成发布前检查、版本管理和提交流程。
| name | github |
| description | Prepare GitHub issues, pull requests, reviews, and release notes for Zhin projects. Use when asked to write an issue, PR description, changelog entry, or review comment. Triggers: 写 issue, PR 描述, 提 PR, release notes, gh pr. |
| keywords | ["github","issue","pull request","pr","release notes","写 issue"] |
| tags | ["github","collaboration","documentation"] |
为 Zhin 生态仓库生成可直接粘贴的 GitHub 文案（Issue / PR / Review / Release），不代替 gh 执行发布。
[area] 简短问题陈述（area 如 agent / adapter-icqq / cli）## 环境
- Node: v24.x
- zhin.js / @zhin.js/*: （版本或 commit）
- 适配器: icqq / telegram / ...
- OS: macOS / Linux
## 复现步骤
1. ...
2. ...
## 期望行为
...
## 实际行为
...
## 日志 / 截图
（脱敏；无 token）
## Summary
- ...
## Test plan
- [x] `pnpm --filter @zhin.js/core test`
- [x] `pnpm type-check`
- [ ] `pnpm test`（如未跑则写原因）
## Risk
- Breaking: `zhin.config` `bots` → `endpoints`（如适用）
- DB: 自动迁移 `bot_id` → `endpoint_id`（如适用）
## Changeset
- [ ] 已添加 changeset（monorepo 发布包时必填）
pnpm --filter <pkg> build
pnpm --filter <pkg> test
pnpm type-check
pnpm check:architecture # 跨层改动时
Added / Changed / Fixed / Breakingbots: → endpoints:）| 触发条件 | 一线处理 | 仍失败 |
|---|---|---|
| 信息不足 | 列出缺失项（版本、配置、日志），🔴 暂停生成 | 用户补充后再写 |
| 含 token/密钥 | 删除敏感字段，用 <REDACTED> 占位 | 提醒用户轮换已泄漏凭证 |
gh 不可用 | 只输出 Markdown；给出 gh issue create / gh pr create 示例命令 | 用户手动在网页创建 |
生成前扫描：API token、.env 内容、私聊 ID、内网 URL。命中则不得写入 Issue/PR 正文。
zhin.config.yml 密钥packages/im 分层术语用户要求代发时，在项目根用 gh（需已 gh auth login）：
gh issue create --title "..." --body-file /tmp/issue.md
gh pr create --title "..." --body-file /tmp/pr.md
| 文档 | 路径 |
|---|---|
| 贡献与 PR 流程 | docs/agents/issue-tracker.md |
| Changeset | 根目录 pnpm changeset |
| 架构约束 | AGENTS.md |