地址审查
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
运行 `git branch --show-current` 获取当前分支。派生功能文件夹:从分支名称中去除 `feat/` 前缀。提取第一个路径段(第二个`/`之前的所有内容)——这是特征段。功能文件夹 = `spec/features/[slug]/`
使用`gh api repos/{owner}/{repo}/pulls/{number}/comments`获取所有评论意见。过滤未解决/待处理的评论(作者尚未解决)。按类别对评论进行分组: 代码评论 一般代码审查反馈 - bug、风格、逻辑问题、建议。
对于每个未解析的代码注释:读取引用的文件和行范围。理解审稿人的担忧。修复代码以解决问题。如果修复需要测试更改,请更新测试并确保它们通过。
从功能文件夹(如果存在)中读取`SPEC-PROPOSAL.md`。对于已批准的提案,请阅读提案条目(例如 SP-001)。将建议的更改应用于实际规范文件(例如,更新功能文件夹中的`REQUIREMENTS.md`、`ADR.md`或`DESIGN.md`)。从`SPEC-PROPOSAL.md`中删除已批准的条目。
运行完整的测试套件(或至少与更改相关的测试)以确保修复后一切都通过。
暂存所有修改的文件。提交消息:`fix(NNNN-slug): address review comments for {ISSUE-ID}` 推送到当前分支。
提出摘要: 所处理的评论数量 代码更改 批准/拒绝的规范提案以及更新的文件 SPEC-PROPOSAL.md 是否已清理
# Address Review
This skill pulls unresolved review comments from the current branch's PR and addresses them. It handles code changes, spec proposal approvals, and pushes fixes.
## Process
### Step 1: Identify the PR and Feature Folder
1. Run `git branch --show-current` to get the current branch.
2. Derive the feature folder:
- Strip the `feat/` prefix from the branch name.
- Extract the first path segment (everything before the second `/`) — this is the feature slug.
- Feature folder = `spec/features/[slug]/`
- Example: `feat/0023-payment-retry/eng-123-retry-endpoint` → `spec/features/0023-payment-retry/`
- Example: `feat/0023-payment-retry` → `spec/features/0023-payment-retry/`
3. Use `gh pr view --json number,url,headRefName` to find the open PR for this branch.
4. If no PR is found, fail with a clear message.
### Step 2: Pull Unresolved Comments
1. Use `gh api repos/{owner}/{repo}/pulls/{number}/comments` to get all review comments.
2. Filter for unresolved/pending comments (not yet resolved by the author).
3. Group comments by category:
#### Code Comments
General code review feedback — bugs, style, logic issues, suggestions.
#### Spec Proposal Comments
Comments that reference SPEC-PROPOSAL.md entries. Look for patterns like:
- "SPEC-PROPOSAL: approved" or "SP-001: approved" — reviewer approves the proposal
- "SPEC-PROPOSAL: rejected" or "SP-001: rejected" — reviewer rejects the proposal
- Other comments on SPEC-PROPOSAL.md lines
### Step 3: Address Code Comments
For each unresolved code comment:
1. Read the referenced file and line range.
2. Understand the reviewer's concern.
3. Fix the code to address the concern.
4. If the fix requires test changes, update tests and ensure they pass.
5. If the fix changes behavior covered by `spec://` references, verify the references are still correct.
### Step 4: Handle Spec Proposals
Read `SPEC-PROPOSAL.md` from the feature folder (if it exists).
#### For Approved Proposals
1. Read the proposal entry (e.g. SP-001).
2. Apply the proposed change to the actual spec file (e.g. update `REQUIREMENTS.md`, `ADR.md`, or `DESIGN.md` in the feature folder).
3. Remove the approved entry from `SPEC-PROPOSAL.md`.
#### For Rejected Proposals
1. Read the rejection reason from the review comment.
2. Revert any code that was written assuming the proposed spec change.
3. Adjust the implementation to work within the existing spec.
4. Remove the rejected entry from `SPEC-PROPOSAL.md`.
5. Update tests if the behavior changed.
#### Cleanup
If all entries in `SPEC-PROPOSAL.md` are resolved (approved or rejected), delete the file entirely.
### Step 5: Run Tests
Run the full test suite (or at minimum, tests related to the changes) to ensure everything passes after the fixes.
### Step 6: Commit and Push
1. Stage all modified files.
2. Commit with message: `fix(NNNN-slug): address review comments for {ISSUE-ID}`
3. Push to the current branch.
### Step 7: Report
Present a summary:
- Number of comments addressed
- Code changes made
- Spec proposals approved/rejected and files updated
- Whether SPEC-PROPOSAL.md was cleaned up
- Test results
- Suggest running `/address-review` again after the next review cycle
- If all comments are resolved and PR is approved, remind the user to merge the PR manually
---
> Source: [aqaliarept/sdd](https://github.com/aqaliarept/sdd) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
按说明文件中的顺序排列。
第 1 步:识别 PR 和功能文件夹
第 2 步:拉取未解决的评论
步骤 3:地址代码注释
第 4 步:处理规格提案
第 5 步:运行测试
文件/命令 -> git branch --show-current · feat/ · spec/features/[slug]/ · feat/0023-payment-retry/eng-123-retry-endpoint · spec/features/0023-payment-retry/ · feat/0023-payment-retry · gh pr view --json number,url,headRefName · gh api repos/{owner}/{repo}/pulls/{number}/comments
内容校验值 -> 4f4481b2a324
当前原文的自动摘译,尚未人工审校。
第 4 步:处理规格提案
从功能文件夹中读取
SPEC-PROPOSAL.md(如果存在)。对于已批准的提案,请阅读提案条目(例如 SP-001)。将建议的更改应用于实际规范文件(例如,更新功能文件夹中的REQUIREMENTS.md、ADR.md或DESIGN.md)。从SPEC-PROPOSAL.md中删除已批准的条目。