Agent skill

Review Cycle

by bholmesdev in bholmesdev/hubble.md

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.

MITAuto-check passedDevelopment

Install Review Cycle

skills CLI
$ npx skills add bholmesdev/hubble.md --skill review-cycle -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bholmesdev/hubble.md review-cycle --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bholmesdev/hubble.md.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/review-cycle .claude/skills/review-cycle && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
review-cycle
GitHub stars
1.5k
Token cost
~305 tokens
SKILL.md length
164 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 5 steps: Check for review comments sent via the… → Fix actionable findings. → Resolve threads after verifying the fix.… → …
  • A one-off PR review
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Pull requests

What it does

Review Cycle is an agent skill from bholmesdev/hubble.md. 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.

Its SKILL.md is about 310 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: The best notepad for you and your agents. The licence is MIT.

When your agent uses it

  • A one-off PR review
  • Tasks that involve Pull requests

Example prompts

  • “/review-cycle”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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…
  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…

What it can do on your machine

Read from SKILL.md and the folder at commit 571a523. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Review Cycle loads about 305 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 164 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~305

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bholmesdev/hubble.md at commit 571a523, republished under its MIT licence (© bholmesdev). 164 words, ~305 tokens.

Download SKILL.mdSave it as .claude/skills/review-cycle/SKILL.md (or your agent's skills folder).
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.

© bholmesdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/review-cycle of bholmesdev/hubble.md.

Open the folder on GitHubat commit 571a523

Compare with similar skills

Review Cycle next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Review Cycle compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review Cycle this skillbholmesdev/hubble.md1.5k—~305Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from bholmesdev/hubble.md

All 13 skills in this repo
  • Changelog

    bholmesdev/hubble.md

    Add a user-facing entry to CHANGELOG.md for work that just landed.

    1.5k GitHub stars~564 tokensUpdated 6 days ago
    Auto-check passed
  • Review PR

    bholmesdev/hubble.md

    Review a pull request or local branch diff for correctness, security, lifecycle, error handling, tests, and meaningful performance risks.

    1.5k GitHub stars~800 tokensUpdated 6 days ago
    Auto-check passed
  • Triage

    bholmesdev/hubble.md

    Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related issues, then return a structured decision with exactly one triage state.

    1.5k GitHub stars~1.5k tokensUpdated 6 days ago
    Auto-check passed
  • Simplify

    bholmesdev/hubble.md

    Use this skill automatically when you feel your code is ready for human review, and whenever writing or reviewing code comments.

    1.5k GitHub stars~886 tokensUpdated 6 days ago
    Auto-check passed
  • Write Product Spec

    bholmesdev/hubble.md

    Write a PRODUCT.md spec for a significant Hubble user-facing feature, focused only on user experience and observable behavior.

    1.5k GitHub stars~966 tokensUpdated 6 days ago
    Auto-check passed
  • Taste Review

    bholmesdev/hubble.md

    Ask Claude Code to make a taste-driven call on something ambiguous — UI polish, prose phrasing, naming, formatting.

    1.5k GitHub starsUsed in 1 repo~306 tokens
    Auto-check passed

Categories

Questions about Review Cycle

What does Review Cycle do?

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. md. 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.

When should I use Review Cycle?

Review Cycle fits situations like: A one-off PR review; tasks that involve Pull requests.

How do I install Review Cycle in Claude Code?

Run `npx skills add bholmesdev/hubble.md --skill review-cycle -a claude-code`. Or copy the skill folder (.agents/skills/review-cycle in bholmesdev/hubble.md) into .claude/skills/review-cycle in your project. Claude Code loads it when a task matches its description.

How do I install Review Cycle in Codex?

Run `npx skills add bholmesdev/hubble.md --skill review-cycle -a codex`. Or copy the skill folder (.agents/skills/review-cycle in bholmesdev/hubble.md) into .agents/skills/review-cycle in your project. Codex loads it when a task matches its description.

Can I use Review Cycle in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bholmesdev/hubble.md --skill review-cycle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-cycle, .gemini/skills/review-cycle, .github/skills/review-cycle and .opencode/skills/review-cycle in your project.

What does Review Cycle need to run?

SKILL.md names no scripts, command-line tools or credentials: Review Cycle is instructions for the agent only.

Does Review Cycle access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Review Cycle safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Review Cycle use?

Review Cycle is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review Cycle use?

About 305 tokens (SKILL.md is roughly 1.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Review Cycle?

Skills that share tags, products or a category with Review Cycle: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Cycle?

bholmesdev (a GitHub user) maintains it in bholmesdev/hubble.md, which has 1,483 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 1, 2026.

Source: bholmesdev/hubble.md on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.