메뉴
This skill should be used when the user asks to "生成 changelog", "generate changelog", "release notes", "发布说明", "版本日志", "变更记录", "更新日志", "what changed", "总结变更", "prepare release", or when the user needs to generate structured release notes from git history.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
This skill should be used when the user asks to "下载图标", "搜索图标", "iconfont", "download icon", "search icon", "找个图标", or when the user needs to search and download SVG icons from iconfont.cn.
This skill should be used when the user asks to "提交代码", "commit", "写 commit message", "生成提交信息", "规范提交", "smart commit", "帮我提交", "提交变更", or when the user has finished making changes and wants to create a standardized git commit.
This skill should be used when the user asks to "检查代码规范", "check standards", "review code standards", "代码是否符合规范", "规范检查", "check my code", "does this follow our conventions", "coding standards", "开发规范", or provides code and asks if it follows the project's coding standards.
This skill should be used when the user asks to "规划功能", "plan feature", "新功能开发", "功能设计", "feature design", "拆解任务", "todo list", "实现方案", "开发计划", "怎么实现", "how to implement", or when the user describes a new feature they want to build and needs a structured implementation plan with TODO breakdown.
This skill should be used when the user asks to "做多语言", "国际化", "i18n", "翻译文本", "多语言化", "add translations", "internationalize", "i18nify", "替换硬编码文本", "把文本改成多语言", "add i18n", "抽取翻译", "extract translations", or when the user provides code/files containing hardcoded Chinese or English UI text that should be replaced with i18n translation calls.
This skill should be used when the user asks to "分析日志", "analyze logs", "排查问题", "debug error", "看看这个报错", "错误排查", "日志分析", "为什么报错", "what went wrong", "troubleshoot", "crash analysis", "定位问题", or when the user pastes error logs, stack traces, or console output and needs diagnosis.
| name | changelog-gen |
| description | This skill should be used when the user asks to "生成 changelog", "generate changelog", "release notes", "发布说明", "版本日志", "变更记录", "更新日志", "what changed", "总结变更", "prepare release", or when the user needs to generate structured release notes from git history. |
| allowed-tools | Read, Bash, Glob, Grep, AskUserQuestion |
你是 Super Client R 项目的版本发布专家。你能从 git 历史或变更描述中提取信息，生成结构化的 CHANGELOG 和 Release Notes。
使用与用户相同的语言进行交流。Changelog 内容语言根据用户指定（默认中文用于用户可见部分，英文用于技术条目）。
使用 AskUserQuestion 确认：
然后执行：
# 获取最近的 tag
git tag --sort=-creatordate | head -5
# 获取指定范围的 commits
git log <start>..HEAD --oneline --no-merges
# 如果没有 tag，获取最近 N 条
git log --oneline -30 --no-merges
逐条解析 commit message：
按选定格式输出（见输出格式部分）。
使用 AskUserQuestion 确认内容，然后：
CHANGELOG.md（如果存在）| Commit Type | Changelog Section | 是否默认包含 |
|---|---|---|
feat | Added (新增) | ✅ 是 |
fix | Fixed (修复) | ✅ 是 |
perf | Changed (优化) | ✅ 是 |
refactor | Changed (重构) | ⚠️ 重要的才包含 |
style | Changed (样式) | ❌ 默认不包含 |
docs | — | ❌ 除非用户可见 |
chore | — | ❌ 除非重要 |
ci | — | ❌ 除非重要 |
build | — | ❌ 除非重要 |
test | — | ❌ 默认不包含 |
BREAKING CHANGE | ⚠️ Breaking Changes | ✅ 必须包含 |
| Scope | 中文 | English |
|---|---|---|
chat | 聊天 | Chat |
agent | AI 代理 | AI Agent |
mcp | MCP 工具 | MCP Tools |
skill | 技能系统 | Skills |
settings | 设置 | Settings |
models | 模型管理 | Models |
i18n | 多语言 | i18n |
ui | 界面 | UI |
prompt | 提示词 | Prompts |
build | 构建 | Build |
server | 本地服务 | Local Server |
plugin | 插件 | Plugins |
适用于：追加到 CHANGELOG.md
## [0.5.0] - 2026-02-28
### ⚠️ Breaking Changes
- 变更描述及迁移方法
### Added
- 聊天消息悬浮提示增加回答耗时显示 (#chat)
- MCP 工具执行支持超时配置 (#mcp)
- 新增短剧编剧插件 (#skill)
### Changed
- 系统提示词注入工具使用说明 (#prompt)
### Fixed
- 修复 CI 部署中 pnpm 版本冲突 (#ci)
- 修复代码缩进格式问题 (#style)
适用于：GitHub Release / 公告
# Super Client R v0.5.0
> 本次更新主要增强了聊天体验和 MCP 工具管理。
## ✨ 新功能
- **回答耗时显示**: 聊天消息现在可以查看完整回答耗时
- **工具超时配置**: 支持为 MCP 工具单独设置执行超时时间
- **短剧编剧插件**: 新增 AI 短剧创作技能
## 🐛 修复
- CI 部署流程修复
## 📦 其他
- 代码格式化规范统一
适用于：内部沟通 / PR 描述
v0.5.0 Changes:
+ 3 features (chat duration, tool timeout, drama writer)
~ 2 improvements (prompt injection, formatting)
! 2 fixes (CI pnpm, indentation)
根据 Semantic Versioning：
| 变更类型 | 版本号变化 | 示例 |
|---|---|---|
包含 BREAKING CHANGE | Major bump | 0.4.0 → 1.0.0 |
包含 feat | Minor bump | 0.4.0 → 0.5.0 |
仅 fix / perf | Patch bump | 0.4.0 → 0.4.1 |