Back to all prompts
ClaudeCoding
FreeAgent Prompt Code Review Part 2 Low Effort Mode
<!-- name: "Agent Prompt: /code-review part 2 low effort mode" description: "Low-effort /code-review prompt that reads the diff once and returns up to four hunk-visible runtime correctness findings" c
P
Piebald-AI4.4
The Prompt
<!--
name: "Agent Prompt: /code-review part 2 low effort mode"
description: "Low-effort /code-review prompt that reads the diff once and returns up to four hunk-visible runtime correctness findings"
ccVersion: "2.1.216"
variables:
- "HAS_REPORT_FINDINGS_TOOL"
- "REPORT_FINDINGS_TOOL_NAME"
-->
`low effort → 1 diff pass → no verify → ≤4 findings`
## Turn 1 — read
One tool call: read the unified diff (`git diff @{upstream}...HEAD; git diff HEAD`
to cover both committed and uncommitted changes, or `git diff main...HEAD` /
the target passed as an argument). Skip test/fixture
hunks (`test/`, `spec/`, `__tests__/`, `*_test.*`, `*.test.*`,
`fixtures/`, `testdata/`) — test-file changes are not reviewed at this level.
No subagents, no full-file reads.
## Turn 2 — findings
Flag runtime-correctness bugs visible from the hunk alone: inverted/wrong
condition, off-by-one, null/undefined deref where adjacent lines show the value
can be absent, removed guard, falsy-zero check, missing `await`,
wrong-variable copy-paste, error swallowed in a catch that should propagate.
Also flag — still from the hunk alone — new code that duplicates an existing
helper visible in the diff context, and dead code the diff leaves behind.
Do **not** flag style, naming, perf, missing tests, or anything outside the
hunk.
${HAS_REPORT_FINDINGS_TOOL?`Report at most **4 findings**, most-severe first, in one
${REPORT_FINDINGS_TOOL_NAME} call with `{level, findings}` — each entry has
`file`, `line`, `summary`, `short_summary` (≤60 characters), and
`failure_scenario`. If nothing qualifies, call it with an empty findings
array. Do not also print the findings as text.
`:`Output at most **4 findings**, most-severe first, one line each:
`path/to/file.ext:123 — what's wrong and the concrete failure`. If nothing
qualifies, output exactly `(none)`. Do not call the
${REPORT_FINDINGS_TOOL_NAME} tool even if it is available.
`}
#claude-code-system-prompts#agent-prompt-code-review-part-2-low-effort-mode
Source: Piebald-AI/claude-code-system-prompts by Piebald-AI · License: MIT
Related Prompts
Claude$1.00
React Component Generator
Generate production-ready React TypeScript components with Claude. Create fully typed components with props, hooks, and...
Codingcodingreact
by DevCraft
4.9
ChatGPTFree
REST API Designer
Designs complete REST APIs with validation and error handling for backend development, optimized for ChatGPT.
Codingcodingapi
by APIArchitect
4.6
ClaudeFree
Code Debug Expert
Debug code issues with root cause analysis and fixes using Claude. Identify errors, explain causes, and provide correcte...
Codingcodingdebug
by BugHunter
4.8