Have DSH review the changes and list the risks

When to use

Before merging a module or a PR, you want the AI to flag obvious problems and risks, not just say "looks fine".

Preparation

Host version

To fill (record the exact rc version when testing)

Model

To fill

Mode / permissions

Standard mode + modify-within-workspace is enough to start

Plugins required

None (add name & version after testing if used)

Input materials

Keep in a separate workspace; back up originals first

Full instruction

Review the [diff of the current branch against main] and do a code review. Do NOT modify code automatically.

Output format:
1. Risk list: each item has file:line, problem type (null pointer / out-of-bounds / concurrency / resource leak / missing error handling / unsafe call, etc.), why it is a risk, and a suggested fix.
2. Separate must-fix items from suggested items.
3. Flag anything you are unsure about and need a human to confirm; do not decide for me.
4. One-line verdict at the end: mergeable or not.

Requirements: only look at files in the diff and their direct dependencies; no drive-by refactoring; do not modify any file.

Copy full instruction

Run log

Output

After a successful run, list files and screenshots here, and note whether originals changed.

Acceptance checklist

Tap to tick each item off as you verify.

• Only review output was produced; no code was changed
• Each risk item carries file:line and a reason
• Must-fix vs suggested are separated
• Points needing human confirmation are flagged

Failures & boundaries

• For very large diffs, review core files first, then the rest
• The 'mergeable' call is advice; the human decides
• This is a recipe template and has not been tested on this site
• Blocked on: Needs a small real changeset containing a real defect. A synthetic repo validates the flow but not whether it finds genuine problems, which is the entire value of this recipe.

Claim this recipe Back to recipes