公关总结
- 作者仓库星标 2
- 许可证 Apache-2.0
- 作者仓库 ai-dev
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @LLM-Dev-Studio · Apache-2.0
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# PR Summary
This skill generates a structured summary of all changes on the current branch relative to a base branch (default: `master`).
## Workflow
### 1. Gather branch context
```bash
git branch --show-current
git log master..HEAD --oneline
git diff master...HEAD --stat
git log master..HEAD --format="%s%n%b"
```
If the user supplied a different base branch as an argument, substitute it for `master`.
Extract the **work item number** from the branch name (first run of 4+ digits):
| Branch | Work item |
|---|---|
| `feature/12345-add-foo` | `12345` |
| `feedback/58340/from-luke` | `58340` |
| `JTD-56566-missing-screen` | `56566` |
| `docs/59478` | `59478` |
### 2. Analyse the changes
Group changes into logical themes by reading the commit messages and diff stat. Common themes for this project:
- **New features** — new screens, controls, device integrations, service bus consumers
- **Bug fixes** — correctness fixes (mention what was wrong and what was corrected)
- **Renames / breaking changes** — entity or contract renames, API changes
- **Service bus / messaging** — MassTransit consumers, message contracts, RabbitMQ configuration
- **Device integration** — RFID, camera, BlackMoth, or other device changes
- **UI changes** — WPF views, XAML resources, InTruck or Console screens
- **Dead code removal** — deleted files, unused services, obsolete utilities
- **Tooling / config** — CLAUDE.md, skills, CI, migrations, feature flags
### 3. Produce the title and description
**Title** — one line following the project's PR title format: `JTD <work-item> - Brief description`
- Use the work item number extracted from the branch name
- Brief description: imperative, ≤ 70 characters total
- Example: `JTD 58106 - Handle missing RORO bin weights using tipping records`
Output the title first in a code block, then the description below it.
**Description** — output the entire description inside a single fenced markdown code block (` ```markdown `) so the user can copy-paste it directly into Azure DevOps. Use this structure inside the block:
````markdown
```markdown
## Description — Work Item #<id>
### <Theme 1 — e.g. "New Feature: Trailer Management Screen">
- Bullet describing the change. Mention affected components (InTruck, Console, ServiceBus, Shared, Devices) where relevant.
### <Theme 2>
- ...
### Bug Fixes
- **<Short label>** — what was wrong and what was changed to fix it.
### Dead Code / Cleanup
- List deleted files or removed abstractions with a one-line rationale.
### Tooling & Config
- Any non-code changes (CLAUDE.md, skills, CI, feature flags).
---
**Files changed:** X | **Insertions:** +Y | **Deletions:** -Z
```
````
Rules:
- Use `###` headings for each theme; omit sections that have no relevant changes.
- Keep bullets concise — one sentence per item, no padding.
- Always include the `Work Item #<id>` in the description heading.
- Always include the files/insertions/deletions line at the bottom (read from `git diff --stat` summary line).
- If the branch has zero commits ahead of master, say so and exit.
- **The entire description (everything inside the markdown code block) must not exceed 3500 characters.** If the draft exceeds this limit, shorten bullets — summarise groups of related changes into a single bullet, drop minor cleanup items, and abbreviate file lists — until it fits. Never truncate mid-sentence; always produce complete, grammatical bullets.
### 4. Offer next steps
After the summary, ask if the user wants to:
- Create the PR now (`gh pr create`) using the summary as the body
- Review the changes first (`/code-review`)
- Adjust any section of the summary
章节与文件索引
按说明文件中的顺序排列。
1. 收集分支上下文
2. 分析变化
3. 制作标题和描述
<主题 1 — 例如“新功能:预告片管理屏幕”>
<主题2>
文件/命令 -> master · feature/12345-add-foo · 12345 · feedback/58340/from-luke · 58340 · JTD-56566-missing-screen · 56566 · docs/59478
内容校验值 -> f68ac7010cb9
当前原文的自动摘译,尚未人工审校。
1. 收集分支上下文
如果用户提供了不同的基础分支作为参数,请将其替换为
master。从分支名称中提取工作项编号(首行 4 位以上数字): 分支 · 工作项feature/12345-add-foo·12345feedback/58340/from-luke·583402. 分析变化
通过读取提交消息和差异统计数据将更改分组为逻辑主题。该项目的常见主题: 新功能 — 新屏幕、控件、设备集成、服务总线消费者 错误修复 — 正确性修复(指出错误和已纠正的内容) 重命名/重大更改 — 实体或合约重命名、API 更改 服务总线/消息传递 — MassTransit 消费者、消息合约、RabbitMQ 配置
3. 制作标题和描述
标题 — 项目 PR 标题后面的一行 格式:
JTD <work-item> - Brief description使用从分支名称中提取的工作项编号 简要描述:命令式,总共 ≤ 70 个字符 示例:JTD 58106 - Handle missing RORO bin weights using tipping records首先在代码块中输出标题,然后在其下面输出描述。<主题 1 — 例如“新功能:预告片管理屏幕”>
描述更改的项目符号。如果相关,请提及受影响的组件(InTruck、控制台、ServiceBus、共享、设备)。
<主题2>
...