review-fix-loop
This skill should be used when the user asks to "address review feedback", "fix PR comments", "close findings", "respond to reviewer notes", or "reduce review churn". Enforces a finding-to-evidence closure loop for every review round.
来源信息
- 仓库
- spacedriveapp/spacebot
- 最近来源活动
- 2026年2月26日 16:41
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 2,404
- 分支
- 367
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- review-fix-loop
- description
- This skill should be used when the user asks to "address review feedback", "fix PR comments", "close findings", "respond to reviewer notes", or "reduce review churn". Enforces a finding-to-evidence closure loop for every review round.
# Review Fix Loop
## Goal
Close review rounds with minimal back-and-forth by mapping every finding to a code change and proof.
## Execution Loop
1. Parse findings into `P1`, `P2`, `P3`.
2. Build a closure table before editing.
3. Implement the smallest coherent fix batch.
4. Run targeted verification.
5. Update closure table with outcomes.
6. Run broader gate checks.
## Closure Table
Use one row per finding:
| Finding | Severity | Owned files | Planned change | Verification command | Result |
|---|---|---|---|---|---|
## Re-Run Control
- If the same command fails twice, stop rerunning.
- Isolate a smaller reproduction command.
- Patch the smallest likely cause.
- Re-run narrow verification before broad checks.
## Verification Ladder
- Start narrow: unit/module behavior checks for touched paths.
- Continue medium: compile/lint/type checks for touched surfaces.
- End broad: repository gate commands.
## Handoff Requirements
- Findings closed
- Commands executed
- Pass/fail evidence per finding
- Remaining open findings with rationale
- Residual risk
在 GitHub 查看