helixir: Command for Claude Code

.claude/commands/review-pr.md

review-pr is a command for Claude Code from bookedsolidtech/helixir. It costs 0 tokens per session (1,529 once invoked), scanned A, original, MIT.

A command that reviews a GitHub pull request, which is a proposed set of code changes, and posts one grouped review with inline comments.

In plain words
What is it for?
Fetching a pull request's diff, running code-reviewer analysis, posting a batched inline review, and optionally marking a JSONL task complete.
Why use it?
It collects the change set and review analysis in one workflow, then presents the findings in the project owner's voice.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is bookedsolidtech/helixir's own configuration. It tells Claude Code how to work on helixir itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything helixir configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bookedsolidtech/helixir. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/bookedsolidtech/helixir/main/.claude/commands/review-pr.md
Clone the repo
git clone --depth 1 https://github.com/bookedsolidtech/helixir

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for review-pr

README.md
[![agentmods](https://agentmods.dev/badge/commands/bookedsolidtech/helixir/review-pr/github.svg)](https://agentmods.dev/commands/bookedsolidtech/helixir/review-pr)
Your own site
<a href="https://agentmods.dev/commands/bookedsolidtech/helixir/review-pr"><img src="https://agentmods.dev/badge/commands/bookedsolidtech/helixir/review-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for review-pr

Your own site · 80×15
<a href="https://agentmods.dev/commands/bookedsolidtech/helixir/review-pr"><img src="https://agentmods.dev/badge/commands/bookedsolidtech/helixir/review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,529 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01529
Opus 5.5 $0.00000 $0.00612
Sonnet 5.5 $0.00000 $0.00306
Haiku 4.5 $0.00000 $0.00153

Measured 2mo ago against content hash abd5c25bd741, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/review-pr.md · 198 lines

How it starts

The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fetch a pull request diff, run code-reviewer analysis, translate findings to owner voice, and post a single batched inline GitHub review.

Usage

/review-pr <PR#> [--tier standard|senior|chief] [--task T-NNN]

Arguments:

  • <PR#> — pull request number (required)
  • --tier — review depth: standard (default), senior, or chief
  • --task — optional JSONL task ID to mark completed after the review posts (e.g. --task T-047)

Step 1 — Check prerequisites

Before anything else:

  1. Read .rea/policy.yaml — confirm autonomy level is L1 or higher
  2. Check for .rea/HALT — if present, stop immediately
  3. Verify gh CLI is available: gh --version
  4. Confirm caller is in a git repo with a GitHub remote: gh repo view --json nameWithOwner

Extract owner/repo for use in API calls.


Step 2 — Fetch PR context

Run these in parallel:

gh pr view <PR#> --json title,body,headRefName,baseRefName,state,commits
gh pr diff <PR#>
gh pr view <PR#> --json commits --jq '.commits[-1].oid'

Store:

  • COMMIT_SHA — the latest commit OID (use in the review payload)
  • PR_TITLE — for context
  • PR_DIFF — the full diff text (pass to code-reviewer)

If the PR is merged or closed, warn the user: "PR #N is already closed — review will post but won't block a merge."

If gh pr diff returns an empty diff, stop and report: "Empty diff — nothing to review."


Step 3 — Run code-reviewer analysis

Invoke the code-reviewer agent with the diff and the specified tier.

Pass this context to code-reviewer:

Tier: <standard|senior|chief>

Review the following git diff and produce structured findings as a JSON array.
Each finding must include:
  - file: string (file path from diff header)
  - line: number (line number in the NEW file)
  - start_line?: number (for multi-line spans, the start line)
  - severity: "high" | "medium" | "low"
  - issue: string (the specific problem — no hedging)
  - suggestion_code?: string (the corrected code, if applicable)

Output ONLY the JSON array. No prose. No markdown wrapper. Example:
[
  {
    "file": "src/gateway/middleware/chain.ts",
    "line": 42,
    "severity": "high",
    "issue": "Non-null assertion will throw if upstream returns undefined",
    "suggestion_code": "const result = upstream ?? defaultValue;"
  }
]

If there are no findings, output: []

DIFF:
<paste full diff here>

Read the full file on GitHub · 198 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 198 lines · 0 tokens per session scan A abd5c25bd741

Subscribe to this mod's changes

review-pr is a command published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,529 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.