review-cycle
Work through code-review feedback on an open PR until checks and review threads settle, after the user says the work is ready for their review. Do not use for a one-off PR review.
소스 정보
- 저장소
- bholmesdev/hubble.md
- 최근 소스 활동
- 2026년 9월 26일 19:56
- 감지된 SKILL.md 언어
- 영어
- 스타
- 1,483
- 포크
- 96
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- review-cycle
- description
- Work through code-review feedback on an open PR until checks and review threads settle, after the user says the work is ready for their review. Do not use for a one-off PR review.
# Review cycle
Use this after the human decides a feature or PR is ready for their review.
1. Check for review comments sent via the code review agent on GitHub.
2. Fix actionable findings.
3. Resolve threads after verifying the fix. For feedback that does not apply, explain why; leave the thread open if a decision remains contested.
4. Wait for checks and any configured automated reviews of the new commit, then fetch the threads again. Repeat for new actionable findings.
5. Hand the PR to the human only when required checks have finished and no actionable review thread remains unresolved. Report the PR link, fixes, and validation. If a product decision or external failure blocks the cycle, state the concrete blocker without claiming the review is settled.
Do not broaden the PR or make speculative changes to satisfy a reviewer. If a reviewer repeatedly raises an invalid finding, explain the evidence once and surface the disagreement to the human instead of looping indefinitely.
GitHub에서 보기