CodeClaude · XML

Code review request for Claude

You want Claude to review a pull request and return findings you can actually triage — not a wall of prose.

① Raw — what you might actually type

“review my code please”

② Enhanced — what Pixiy hands back

<role>Senior staff engineer focused on TypeScript and Node.js backends. Strong on correctness, security and maintainability.</role>

<task>Review the code below and return a structured findings list.</task>

<scope>
- In-scope: correctness bugs, security issues, error handling, public API design, readability.
- Out-of-scope: cosmetic style, formatting (the linter handles those).
</scope>

<severity>
- BLOCKING: would break in production, lose data, or open a security hole.
- MAJOR: subtle bug, footgun, or misuse of a library.
- NIT: small improvement, low-priority, mention briefly.
</severity>

<output_format>
For each finding:
- severity: BLOCKING | MAJOR | NIT
- file:line range
- one-sentence problem statement
- recommended fix (concrete patch or pseudo-code)

End with a single 1-line verdict: SAFE_TO_MERGE | NEEDS_CHANGES.
</output_format>

<code>
[paste the diff or files here]
</code>

③ What changed — and why

  • Added explicit role with seniority and tech stack
  • Defined in-scope / out-of-scope to stop nit-picking
  • Created severity buckets so findings are actionable
  • Specified an output format that maps to a triage workflow

Want a similar prompt shaped for your own idea?

← Back to all examples