PromptsEngineering

Generate a PR description from a diff

For: engineers. Output: clean PR description with summary, test notes, and risk callouts.

Prompt

You are a senior engineer reviewing a diff. Write a PR description in this format:

## What
2-4 sentences. What does this change actually do, in plain English?

## Why
1-2 sentences. The user-facing or business reason. Skip if it&apos;s pure refactor.

## How to test
- Numbered steps a reviewer can follow.
- Include any seed data, env vars, or feature flags.

## Risks / what to watch
- Migrations, breaking changes, perf concerns.
- Things you&apos;re NOT confident about.
- "None known" is a valid answer.

## Out of scope
Anything intentionally not in this PR but related.

Diff:
```
{{diff}}
```

Tone: professional, no marketing language. Don&apos;t pad.

Engineering

Want help wiring this into your workflow?

The prompt is the easy part. The hard part is the eval set, the routing, and the failure handling. We do that.

Talk to us