Menü
汇总审查结果，给出建议操作。支持 GitHub 模式和本地模式。支持中文触发：审查PR、PR审查、查看审查结果、PR建议。
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | pdd-pr-review |
| description | 汇总审查结果，给出建议操作。支持 GitHub 模式和本地模式。支持中文触发：审查PR、PR审查、查看审查结果、PR建议。 |
| author | neuqik@hotmail.com |
| license | MIT |
Description: 汇总审查结果，给出建议操作。支持 GitHub 模式和本地模式。
Details: 查看 PR 审查结果和建议
Input: OpenSpec Change ID 或 PR 编号
GitHub 模式:
├── 从 GitHub API 获取 PR 信息
├── 获取 PR 状态、评论、检查结果
└── 获取关联的 Change ID
本地模式:
├── 读取 pr-record.md
├── 解析审查记录
└── 获取 Change ID
读取: openspec/changes/{change-id}/review-report.md
解析:
├── Blocking 问题数量
├── Warning 问题数量
├── Suggestion 数量
├── 测试覆盖率
└── 各检查项状态
统计:
├── Blocking 问题: 0 → ✅ 可合并
├── Warning 问题: ≤3 → ⚠️ 建议修复后合并
└── Warning 问题: >3 → ❌ 建议修复
判断逻辑:
├── 无 Blocking + Warning ≤ 3 → 建议: 通过
├── 有 Blocking → 建议: 需修复
└── Warning > 3 → 建议: 建议修复
输出:
├── 审查结果汇总表
├── 问题列表（可选详细模式）
├── 建议操作
└── 等待用户决策
## PR 审查报告
**PR 编号**: #123
**Change ID**: c-001-xxx
**标题**: feat(workflow): 添加权限控制
### 审查结果汇总
| 级别 | 数量 | 状态 |
|------|------|------|
| 🔴 Blocking | 0 | ✅ |
| 🟡 Warning | 2 | ⚠️ |
| 💡 Suggestion | 3 | ℹ️ |
### 建议操作
**✅ 可以合并** - 无 Blocking 问题，Warning 数量在可接受范围内
### 操作选项
- 确认合并: `/pdd-pr-merge c-001-xxx`
- 修复后重新审查: 修复问题后执行 `/pdd-pr-create c-001-xxx --re-review`
- 查看详细问题: `/pdd-pr-review c-001-xxx --detail`
## PR 审查报告（详细）
**PR 编号**: #123
**Change ID**: c-001-xxx
**标题**: feat(workflow): 添加权限控制
### 审查结果汇总
| 级别 | 数量 | 状态 |
|------|------|------|
| 🔴 Blocking | 0 | ✅ |
| 🟡 Warning | 2 | ⚠️ |
| 💡 Suggestion | 3 | ℹ️ |
### 🟡 Warning 问题
#### [W-001] 方法参数命名不一致
- **文件**: WorkflowController.java:45
- **描述**: 参数名 `userId` 与其他方法不一致
- **建议**: 统一使用 `user_id` 或 `userId`
#### [W-002] 缺少 JavaDoc 注释
- **文件**: WorkflowService.java:78
- **描述**: 公共方法缺少文档注释
- **建议**: 添加方法功能说明和参数说明
### 💡 Suggestion
#### [S-001] 可优化循环逻辑
- **文件**: WorkflowService.java:102
- **描述**: 可使用 Stream API 简化代码
- **建议**: `list.stream().filter(...).collect(...)`
### 测试覆盖详情
| 模块 | 覆盖率 | 状态 |
|------|--------|------|
| asset-admin | 85% | ✅ |
| asset-system | 72% | ✅ |
### 建议操作
**✅ 可以合并**
### 操作选项
- 确认合并: `/pdd-pr-merge c-001-xxx`
- 修复后重新审查: 修复问题后执行 `/pdd-pr-create c-001-xxx --re-review`
| 参数 | 类型 | 必需 | 默认值 | 描述 |
|---|---|---|---|---|
change_id | string | 否 | - | OpenSpec Change ID |
pr_number | number | 否 | - | GitHub PR 编号 |
detail | boolean | 否 | false | 是否显示详细问题列表 |
❌ PR 不存在
**Change ID**: c-001-xxx
请先创建 PR: `/pdd-pr-create c-001-xxx`
❌ 本地 PR 记录不存在
**Change ID**: c-001-xxx
请先创建 PR: `/pdd-pr-create c-001-xxx`
pdd-pr-review
│
├── 被调用方
│ ├── pdd-pr-create (创建后查看)
│ └── 用户直接调用
│
└── 调用方
└── pdd-pr-merge (合并前查看)
本Skill遵循PDD框架实施规范，详见 pdd-framework-design.md 第9章。
Architecture constraint enforcement skill that monitors code for violations of preset invariants and architectural boundaries. Automatically triggered when users need architecture checks, dependency checks, or module boundary checks. Core responsibility: Ensure architectural coherence and prevent architectural drift. Trigger scenarios: - User requests "check architecture constraints", "check dependency direction", "check module boundaries" - Called by pdd-entropy-reduction coordinator - Automatically triggered after code commits 支持中文触发：架构约束检查、依赖检查、模块边界检查、架构强制、架构漂移、PDD架构约束。
Automated refactoring expert skill that transforms collected quality improvement tasks into concrete code operations. Automatically triggers when users need code refactoring, duplicate elimination, or complexity simplification. Core responsibility: Initiate targeted refactoring PRs regularly in a "small debt repayment" manner to prevent technical debt accumulation. Trigger scenarios: - User requests "refactor code", "eliminate duplicates", "simplify code" - Called by pdd-entropy-reduction coordinator - Refactoring suggestions passed from expert-entropy-auditor 支持中文触发：自动重构、代码重构、消除重复、简化代码、重构专家、PDD重构。
Entropy audit skill that discovers the gap between "design intent" and "code implementation". Automatically triggered when users need technical debt audit, PRD and code consistency check, or AI residue detection. Core responsibility: Identify "AI residue" scattered in the codebase and suggest consolidating them into shared utility packages. Trigger scenarios: - User requests "audit technical debt", "check PRD consistency", "detect AI residue" - pdd-entropy-reduction coordinator calls - Scheduled trigger (recommended weekly) 支持中文触发：熵增审计、技术债务审计、PRD一致性检查、AI残渣检测、PDD熵审计。
PDD Entropy Reduction Agent, continuously monitors and repays technical debt to prevent system decay. Automatically triggered when users need code cleanup, documentation updates, technical debt management, architecture alignment, entropy reduction, or garbage collection. Core Objective: Combat system "entropy increase" and "decay" by periodically running agents to discover documentation inconsistencies or architecture constraint violations. Trigger Scenarios: - User requests "entropy reduction", "clean up technical debt", "code cleanup", "garbage collection" - User requests checking documentation and code consistency - User requests architecture constraint checking - User requests technical debt audit - Scheduled trigger (recommended weekly) - Automatic trigger after code commit (optional) - Automatic trigger after PR merge (optional) 支持中文触发：熵减、清理技术债务、代码清理、文档更新、技术债务管理、架构对齐、垃圾回收、PDD熵减。
Activiti workflow engine expert, proficient in Activiti 7 Core/Cloud architecture, BPMN 2.0 specification, process design and development. Automatically triggered when users involve workflow design, process engine development, BPMN modeling, process deployment management and other issues. Provides BPMN modeling, best practices and solutions. 支持中文触发：工作流设计、流程引擎开发、BPMN建模、流程部署管理、Activiti、工作流、流程设计。
Code quality expert integrating Martin Fowler's refactoring techniques and GoF design patterns to help developers systematically improve code quality. Triggers when users ask about code review, refactoring, design patterns, code smells, SOLID principles, or software architecture improvements. 支持中文触发：代码审查、重构、设计模式、代码异味、SOLID原则、软件架构改进、代码质量。