Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/goulinkh/code-review-harness/llms.txt

Use this file to discover all available pages before exploring further.

This guide walks you through installing CRH and running your first AI code review against a Launchpad merge proposal. Before you begin, make sure you have Node.js 20 or later installed and a Launchpad merge proposal URL ready to test with.
1

Install CRH

Install the code-review-harness package globally. This provides both the crh and code-review-harness binary names.
npm install -g code-review-harness
Verify the installation:
crh --version
2

Run a dry-run review to stdout

Run a review against your merge proposal and print the results to stdout. This requires no credentials — it is a safe way to see CRH in action before posting anything to Launchpad.
crh review \
  --provider launchpad \
  --pr "https://api.launchpad.net/devel/~user/+git/repo/+merge/123" \
  --sink stdout
CRH uses anthropic:claude-sonnet-4-6 by default. To use a different model, pass --model <provider>:<model-id>. For example:
crh review \
  --provider launchpad \
  --pr "https://api.launchpad.net/devel/~user/+git/repo/+merge/123" \
  --sink stdout \
  --model openai:gpt-4o
The review findings are written as a single JSON line to stdout. Progress and agent thinking stream to stderr.
3

(Optional) Post the review to Launchpad

To post inline comments and a verdict back to the merge proposal, set your Launchpad OAuth credentials and switch the sink to launchpad.
export LP_ACCESS_TOKEN=your-access-token
export LP_ACCESS_SECRET=your-access-secret
export LP_CONSUMER_KEY=crh
Then run the review with --sink launchpad:
crh review \
  --provider launchpad \
  --pr "https://api.launchpad.net/devel/~user/+git/repo/+merge/123" \
  --sink launchpad
The Launchpad sink requires valid OAuth 1.0a tokens. Without them, the request will be rejected by the Launchpad API. See the authentication guide for instructions on obtaining tokens.

​
Next steps

Build docs developers (and LLMs) love

Get started for freeTalk to us