Diff reviewer

What it is

Diff reviewer reads a code diff and lists what is wrong or risky, the worst problem first. It looks for bugs, unhandled edge cases, security problems and missing tests. Each finding says where it is, what goes wrong and when, and the smallest change that fixes it.

Who it suits

Developers who push code without a second reviewer, and anyone who lets a coding agent write changes and wants a check before merging.

Teams with strict review rules can use it as a first pass, never as the sign-off.

Where to use it

Before you push or open a pull request, and on code a coding agent just wrote for you. It is a quick second look, not a stand-in for your tests or a human review.

• Any AI chat: where you paste the skill’s prompt with the diff in place of {{input}}
• Git on your computer: git diff and git diff --staged print the changes
• A pull request: copy its diff from the page
• A coding agent’s session: the change it just made, before you merge it

How to set it up

What you need first:

• Where it runs: any AI chat
• A key: none
• An install: none

1. Sign in to Mindket and press Get it on this listing.
2. In your Mindket account, View shows the prompt to read and copy. This page shows it too.
3. Keep it where you can paste it again: a saved prompt in your chat app, if it keeps them, or a note.

How to use it

Copy the diff, then paste the skill’s prompt into an AI chat with the diff where it says {{input}}. In a Git repository, the first command prints the changes you have not staged and the second the ones you have.

git diff
git diff --staged

Smaller diffs get a closer read. Split a big change into parts.

1. You copy the diff from git or your pull request
2. It goes in place of {{input}}, and the chat’s model reads it
3. Findings come back worst first, each with a fix
4. Or one line: Nothing found

Example

You paste a diff that adds a discount code field to a checkout form, with the skill’s prompt above it.

<the skill’s prompt>
<the diff, as git diff printed it>

A short list comes back, worst first. A finding reads like this: the total can drop below zero when two codes stack, in the named file and line, fixed by clamping the total. When the diff is fine, the whole answer is two words, Nothing found.

For newcomers and experts

If you are new. A diff is the list of lines added and removed in a change. This skill reads it and points at the lines that could break, with a fix for each. Start with a small change you made this week, and check each finding yourself before you act on it.

For experts. The prompt asks for findings ranked by severity, each with file, line, failure condition and the smallest fix, and it skips style. It has no repository, types or tests to run, so it reasons from the diff text alone. Expect false positives where the context lives outside the diff. Keep your test suite as the real gate.

Good to know

• What it sees: only the lines you paste, so a bug that depends on a file outside the diff can slip past
• Style: left out on purpose
• Secrets: keep them out of what you paste, since the diff goes to the model you chat with