code-insights: Command for Claude Code

.claude/commands/start-review.md

start-review is a command for Claude Code from melagiri/code-insights. It costs 0 tokens per session (4,004 once invoked), scanned A, original, MIT.

A command that starts a multi-layer review of a GitHub pull request. A pull request is a proposed code change, and the workflow chooses reviewers based on the parts of the code that changed.

In plain words
What is it for?
Use it to review a pull request, including its title, description, changed files, line counts, schema-related changes, and domain-specific code issues.
Why use it?
It removes the need to manually gather the pull request details, inspect the diff, classify the affected areas, and select suitable reviewers. The review repeats until outstanding fix-now issues are resolved.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md; mentions subagents.

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

Reuse

Borrowing it

Nothing to install: this file belongs to melagiri/code-insights. 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/melagiri/code-insights/master/.claude/commands/start-review.md
Clone the repo
git clone --depth 1 https://github.com/melagiri/code-insights

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/melagiri/code-insights/start-review"><img src="https://agentmods.dev/badge/commands/melagiri/code-insights/start-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 4,004 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.04004
Opus 5.5 $0.00000 $0.01602
Sonnet 5.5 $0.00000 $0.00801
Haiku 4.5 $0.00000 $0.00400

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

Security

Grade A, and why

start-review scanned grade A with 1 finding 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 1mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **For API changes**: curl output showing the endpoint returns the expected response shape
.claude/commands/start-review.md · 376 lines

How it starts

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

/start-review — Triple-Layer Code Review Team

PR: $ARGUMENTS

You are setting up a triple-layer code review for PR $ARGUMENTS. This can be used standalone or as part of a /start-feature team workflow. The review loops until all FIX NOW items are resolved — it does NOT end after a single pass.


Step 1: Get PR Details

Fetch the PR details:

# Get the correct owner from git remote
git remote get-url origin | sed 's/.*[:/]\([^/]*\)\/[^/]*\.git/\1/'

Use gh pr view $ARGUMENTS to get PR title, description, and diff stats. Use gh pr diff $ARGUMENTS to get the diff.

Determine the PR scope:

  • Count files changed and lines changed per file
  • Identify if it touches schema concerns (types.ts, SQLite schema, server API)
  • Classify changed files into domains for specialist selection (Step 2)

Step 2: Select Domain Specialists

Instead of fixed generalist reviewers, select 1-2 domain specialists based on what the PR actually changes. Each specialist combines deep domain expertise with general engineering awareness. See docs/REVIEW-SPECIALISTS.md for the full specialist registry and prompt templates.

Domain Classification

Classify each changed file into a domain based on file patterns:

Domain File Pattern Triggers
SQL/Database server/src/routes/*.ts (when containing SQL keywords), cli/src/db/*.ts
React/Frontend dashboard/src/**/*.tsx, dashboard/src/**/*.ts
Node/CLI cli/src/commands/*.ts, cli/src/utils/*.ts, server/src/*.ts (non-route, non-LLM)
Parser/Provider cli/src/providers/**/*.ts, cli/src/parser/*.ts
LLM server/src/llm/**/*.ts — handled by LLM Expert (separate, unchanged)

Files that don't match any domain (e.g., package.json, tsconfig.json, .gitignore, CLAUDE.md) are ignored during classification.

Selection Algorithm

  1. For each domain, sum the lines changed across all files in that domain
  2. Primary specialist = domain with the most lines changed
  3. Secondary specialist = next domain IF it has >= 30% of total changed lines AND is a different domain
  4. Cap at 2 domain specialists (LLM Expert is a separate conditional reviewer)
  5. If a PR changes ONLY non-domain files, use the Node/CLI Specialist as general-purpose

Read the full file on GitHub · 376 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. 1mo ago First seen · 376 lines · 0 tokens per session scan A ed85be5bee17

Subscribe to this mod's changes

start-review is a command published in the GitHub repository melagiri/code-insights (77 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,004 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.