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,399
- 포크
- 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에서 보기