Impulso: Command for Claude Code

.claude/commands/pr-review.md

pr-review is a command for Claude Code from thomaspinder/Impulso. It costs 0 tokens per session (923 once invoked), scanned A, a copy of pr-review, MIT.

A pull-request review workflow. A pull request is a proposed code change awaiting review before it is merged into a project.

In plain words
What is it for?
Use it to read the project guidance and code diff, then produce structured in-scope and out-of-scope review findings.
Why use it?
It separates problems that should be fixed before merging from worthwhile issues that belong in separate follow-up work.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is thomaspinder/Impulso's own configuration. It tells Claude Code how to work on Impulso 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 Impulso configures →

Reuse

Borrowing it

Nothing to install: this file belongs to thomaspinder/Impulso. 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/thomaspinder/Impulso/main/.claude/commands/pr-review.md
Clone the repo
git clone --depth 1 https://github.com/thomaspinder/Impulso

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 pr-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/thomaspinder/impulso/pr-review/github.svg)](https://agentmods.dev/commands/thomaspinder/impulso/pr-review)
Your own site
<a href="https://agentmods.dev/commands/thomaspinder/impulso/pr-review"><img src="https://agentmods.dev/badge/commands/thomaspinder/impulso/pr-review/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 pr-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/thomaspinder/impulso/pr-review"><img src="https://agentmods.dev/badge/commands/thomaspinder/impulso/pr-review.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 923 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 95% copy Near-identical to another mod 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.00923
Opus 5.5 $0.00000 $0.00369
Sonnet 5.5 $0.00000 $0.00185
Haiku 4.5 $0.00000 $0.00092

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

Security

Grade A, and why

pr-review 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.

Origin

This is a copy

95% identical to pr-review — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

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

How it starts

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

PR Review — In-Scope / Out-of-Scope Audit

You are reviewing a pull request. Your job is to audit the changes and produce a structured review with two clearly separated sections: In-Scope items (things that should be fixed in this PR before merge) and Out-of-Scope items (things worth addressing but belonging in separate issues).

1. Gather context

  • Read the project's CLAUDE.md (root and any directory-level files that share a path with changed files) to understand coding standards and review policy.
  • Run git diff origin/$BASE_REF...HEAD --name-only to list changed files.
  • Run git diff origin/$BASE_REF...HEAD to inspect the full diff.
  • Read the PR title, description, and any linked issues for author intent.

2. Classify findings

In-Scope (must be resolved in this PR)

A finding is in-scope if it meets ANY of the following:

  • It is a bug, logic error, or correctness issue introduced or exposed by this diff.
  • It violates a rule stated in CLAUDE.md and the violation is in a changed file/region.
  • It is a security concern in changed code (injection, auth, data exposure, etc.).
  • It is a missing or broken test for new/changed behaviour.
  • It is a naming, typing, or API-contract inconsistency introduced by this diff.
  • It would block CI or break downstream consumers.

Out-of-Scope (separate follow-up work)

A finding is out-of-scope if it meets ANY of the following:

  • It is pre-existing technical debt not introduced by this diff.
  • It is a refactoring opportunity in unchanged code.
  • It is a performance improvement unrelated to the PR's purpose.
  • It is a feature idea or enhancement inspired by the changes.
  • It is a documentation gap outside the scope of the changed files.
  • It is a broader architectural concern that requires its own design discussion.

When in doubt, classify as out-of-scope — do not block PRs for tangential work.

3. Output format

Structure your review comment as follows. Use exactly this format so it can be parsed by automation:

Read the full file on GitHub · 103 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 · 103 lines · 0 tokens per session scan A 679c699c25d6

Subscribe to this mod's changes

pr-review is a command published in the GitHub repository thomaspinder/Impulso (25 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 923 tokens. A static security scan graded it A with 0 findings. It is 95% identical to pr-review, differing in 6 lines, and is treated as a copy.