reviewer

Reviews diffs and pull requests against architecture and billing rules with read-only verdicts.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill reviewer-lfuuu
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: reviewer
Source: https://github.com/lfuuu/claude-rules/tree/main/ai-billing/skills/reviewer
Command: npx skills add https://github.com/lfuuu/claude-rules --skill reviewer-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes references (resource) components.

What problem does it solve? It provides an independent, read-only code review for the AI Billing MVP, checking diffs and PRs against architectural, billing, and testing rules before merge, and issuing a clear APPROVED or CHANGES_REQUESTED verdict. ## Core Features & Use Cases - Domain Checklist Review: Applies a strict BLOCK/WARN/NOTE checklist covering architecture violations, money handling (decimal.js, no JS number for money), billing invariants (price snapshots, idempotency, transactional consistency), and API contract changes. - Read-Only Verdicts: Never modifies code; outputs APPROVED or CHANGES_REQUESTED with file, line, and category for each finding, with a maximum of two review rounds before escalation. - Use Case: Before committing a new billing calculation feature, invoke this role to verify the diff preserves price snapshots in billing items, keeps idempotency by clientAccountId + sessionId, and includes tests for new business logic. ## Quick Start Ask the reviewer role to check the current diff against the billing and architecture rules and return an APPROVED or CHANGES_REQUESTED verdict.

Frequently Asked Questions about reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a diff against billing architecture rules before committing?ā–¼

Invoke the reviewer role once your diff or patch is final. It checks the change against a domain checklist covering architecture violations, money handling, billing invariants, and test coverage, then returns APPROVED or CHANGES_REQUESTED with file and line references.

What does a code review checklist for a billing system include?ā–¼

This checklist blocks JS number usage for money, missing price snapshots in billing items, broken idempotency by clientAccountId plus sessionId, non-transactional usage and billing saves, silent public API changes, and missing tests for new business logic.

Can the reviewer role run tests or fix the code it reviews?ā–¼

No. The reviewer is strictly read-only: it uses Read, Glob, Grep, and read-only Bash like tsc --noEmit and git diff. Running tests belongs to the testing role, and fixing diffs belongs to the backend or frontend roles.

When should I not invoke a code review role?ā–¼

Do not invoke it while the task is still in progress, since it only reviews final diffs. Also avoid it when you need tests executed or code changes made, as those are handled by separate roles.

What happens if a review keeps returning CHANGES_REQUESTED?ā–¼

The role allows a maximum of two CHANGES_REQUESTED rounds. If BLOCK findings remain after the second round, the issue escalates to the Architect instead of looping through endless fix and retest cycles.