Install and run the review
Set up the Claude Code plugin once, then run one command per pull request.
1. Install the plugin
The plugin is distributed from the hq/hq-rabbit repository, which is private. You need read access to it and git credentials that work without a prompt: for HTTPS run gh auth login and then gh auth setup-git; for SSH, have your key loaded in ssh-agent.
From a terminal:
claude plugin marketplace add hq/hq-rabbit
claude plugin install hq-rabbit@hq-rabbitOr inside a Claude Code session:
/plugin marketplace add hq/hq-rabbit
/plugin install hq-rabbit@hq-rabbitThe plugin follows the repository's latest commit. Update it with claude plugin update hq-rabbit.
2. Run the review
From a checkout of a branch with an open pull request, after pushing:
/hq-rabbit:review # the PR for the current branch
/hq-rabbit:review 123 # a specific PR (number or URL)
/hq-rabbit:review --dry-run # review and print the payload, post nothingThe skill stops without posting when there is no PR, when your local commit is not the PR's head (unpushed or uncommitted changes), or when the PR has no hq-rabbit check. Otherwise it posts the submission, waits for the check to turn green or for a rejection, and reports the findings by severity. Claude Code asks before it runs gh pr comment unless you have allowed it. What the skill does, step by step.
The plugin already knows this server's address; there is nothing to configure. If the skill says it is using the bundled copy of the instructions, it could not reach this server. The review still works with the copy shipped in the plugin; run claude plugin update hq-rabbit to get the latest plugin.
Without Claude Code
Any agent, or a person, that can read a pull request and post a PR comment can submit a review. The plugin is a convenience, not a requirement.
- Review the PR's current head commit against the review instructions (raw markdown: /api/skill/instructions). Look at every changed file.
- Write the payload described in the contract. Its JSON Schema is at /api/contract/v1/schema.json; the contract page lists the few rules the schema cannot express.
- Post one PR comment with the marker line and the fenced JSON block, for example with
gh pr comment <n> --body-file <file>. - Watch the
hq-rabbitcheck. A rejection reply lists the errors to fix before posting a new submission.