What is clean-pr-comments?

A pull-request review command that checks whether code comments are needed or are covering up unclear names or structure.

Use it to find comments that should lead to renaming or refactoring, and to preserve comments that explain facts the code cannot show.

It reduces comments that merely repeat the code while keeping notes about business rules, external problems, performance, or history.

clean-pr-comments — Command by bengous

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/bengous/claude-code-plugins/clean-pr-comments

Clone the repo

git clone --depth 1 https://github.com/bengous/claude-code-plugins

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 763 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00011	$0.00763
Opus 5	$0.00005	$0.00381
Sonnet 5	$0.00002	$0.00153
Haiku 4.5	$0.00001	$0.00076

Measured yesterday against content hash 9c15b97dd043, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

clean-pr-comments 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 yesterday.

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.

code-quality/commands/clean-pr-comments.md · 108 lines

How it starts

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

Clean PR Comments

Review comments in a PR. Fix comments that compensate for bad naming. Preserve comments that provide context code cannot express.

Decision Framework

Comment compensates for...	Action
Bad variable/function name	Rename, remove comment
Missing abstraction	Extract to well-named function, remove comment
External knowledge	Keep
Inherent complexity	Keep

Remove After Refactoring

Comments that explain WHAT code does—these are naming problems:

int d; // days elapsed → rename to elapsedDays
// check if user can access premium before condition → extract to canAccessPremium()
setTimeout(fn, 86400000); // 24 hours → const ONE_DAY_MS = 86400000

Keep

Comments that explain what code CANNOT express:

Business rules: // FCC requires 30-day retention minimum
External quirks: // Safari bug, see webkit#12345
Performance: // Intentionally avoiding map() - 10x faster here
History: // Tried recursion but hit stack limits
Spec constants: // 0x1F frame delimiter per RFC 7230
Warnings: // Order matters - auth before session init
License headers and public API docs

Remove Immediately

Commented-out code (use git history)
Restates code literally: i++ // increment i
TODOs that should be tickets

Workflow

Identify scope:
```
git diff --stat origin/main...HEAD
```
Select strategy based on PR size:
- ≤10 files: Process sequentially yourself
- >10 files: Spawn parallel agents (see Scaling below)
Read each file, identify all comments

Present findings before editing:

src/auth.js:
  L45: "// convert to uppercase" → REMOVE (obvious from code)
  L67: "// api timeout" → REFACTOR: rename `t` to `apiTimeoutMs`
  L89: "// Safari workaround #234" → KEEP (external quirk)

Implement after user confirms
Verify tests pass

Read the full file on GitHub · 108 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.

yesterday First seen · 108 lines · 11 tokens per session scan A 9c15b97dd043

Subscribe to this mod's changes

clean-pr-comments is a command published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 763 once invoked, about $0.0001 per session on Opus 5. 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.

Code review Productivity automation claude-code developer-tools workflow

clean-pr-comments

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Clean PR Comments

Decision Framework

Remove After Refactoring

Keep

Remove Immediately

Workflow

What this file has done since we first saw it

Other commands, from other repositories

pr-address

plan-save

enforce_standards

OPSX: Sync

context

OPSX: Verify