Review cycle
SkillDev toolsWork 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.
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Review cycle skill
What this skill tells your AI
The instructions your AI receives, as published by bholmesdev/hubble.md in .agents/skills/review-cycle/SKILL.md and read by ahel’s review.
Use this after the human decides a feature or PR is ready for their review.
- Check for review comments sent via the code review agent on GitHub.
- Fix actionable findings.
- Resolve threads after verifying the fix. For feedback that does not apply, explain why; leave the thread open if a decision remains contested.
- Wait for checks and any configured automated reviews of the new commit, then fetch the threads again. Repeat for new actionable findings.
- 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.
Signals
- GitHub stars
- 1k
- Forks
- 95
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
review-cycle- Source
- github.com/bholmesdev/hubble.md
github.com/bholmesdev/hubble.md