菜单
Use when writing or updating release notes for a new version, or when summarizing git commit history into a changelog
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards.
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.
Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.
Comprehensive quality verification: spec compliance, lint, type-check, tests, cross-layer data flow, code reuse, and consistency checks. Use when code is written and needs quality verification, before committing changes, or to catch context drift during long sessions.
Wrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal. Use when done coding and ready to end the session.
Understand and customize the local Trellis architecture inside a user project. Use when modifying .trellis plus platform hooks, settings, agents, skills, commands, prompts, workflows, the channel runtime (trellis channel), bundled runtime agents under .trellis/agents/, selectable workflow templates, registry-backed spec refresh, cross-session memory (trellis mem) generated by trellis init, or AI-facing bundled skills (trellis-channel, trellis-session-insight, trellis-spec-bootstrap) and bundled-skill auto-dispatch flow.
| name | writing-release-notes |
| description | Use when writing or updating release notes for a new version, or when summarizing git commit history into a changelog |
从 git 提交历史中提取用户可见的变更，按约定式提交类型分类，编写格式统一的 release note。
获取用户提到的起始和结束 commit，如果没有就要求用户提供范围，不要假设，使用 git log <start>..<end> 查看范围内的所有提交。
对每个提交执行 git show <hash> --stat，理解实际变更内容：
记录的类型：
| 类型 | emoji | 前缀 | 说明 |
|---|---|---|---|
| 新功能 | ✨ | feat | 用户可感知的新增功能 |
| 修复 | 🐛 | fix | Bug 修复 |
| 性能 | ⚡ | perf | 性能优化 |
| 重构 | ♻️ | refactor | 用户可感知的重构（如交互变更） |
跳过的类型：
chore：构建/工具/依赖等内部维护doc/docs：纯文档变更refactor：仅内部代码整理且用户不可感知的每条格式：
- <emoji> <type>: <描述>
描述原则：
示例：
- 🐛 fix: 修复框选命中判断，从仅 AABB 判断改为基于笔迹几何与压感宽度计算，避免误选斜线和压感笔迹
- ✨ feat: 添加应用数据清理功能，启动时自动清理过期的下载安装包与旧版本图标缓存
按以下优先级排列：
同类型内按重要性排序，重要变更靠前。
同时生成中文和英文两个文件，放在 docs/release-notes/ 目录下：
v<版本号>.zh-CN.mdv<版本号>.en-US.md中文模板：
# 更新内容（v<版本号>）
- ✨ feat: ...
- 🐛 fix: ...
- ⚡ perf: ...
- ♻️ refactor: ...
# 已知问题
- 位于v1.x版本的用户直接覆盖安装可能会有未知兼容性问题，建议完全卸载旧版并重装。
英文模板：
# Release Notes (v<版本号>)
- ✨ feat: ...
- 🐛 fix: ...
- ⚡ perf: ...
- ♻️ refactor: ...
# Known Issues
- Users upgrading directly from v1.x by overwriting the installation may encounter unknown compatibility issues. It is recommended to completely uninstall the old version and reinstall the new one.
| 错误 | 正确做法 |
|---|---|
| 直接复制 commit message 作为条目 | 转化为面向用户的描述 |
| 记录所有 refactor 提交 | 仅记录用户可感知的重构 |
| 将一个 commit 的多个修复混为一条 | 拆分为独立条目，方便用户检索 |
| 遗漏已知问题章节 | 保留已知问题，如无新增则沿用上一版 |