Skip to content
Back to skills

Review Diff

ASecurity

Open the current git diff for inline review in a local surface and return the annotations. Use when a person should review a change before it proceeds.

  • 4 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 19, 2026
ai-agentsgit

Security analysis

A100/100

Scanned September 19, 2026

npx -y skills add jonny981/obversa --skill review-diff --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Review Diff?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Review Diff
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jonny981-review-diff/badge)](https://www.skillsdirectory.com/skills/jonny981-review-diff)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: review-diff
description: Open the current git diff for inline review in a local surface and return the annotations. Use when a person should review a change before it proceeds.
---

## Launch

Run from the repository under review and keep the command running until the
reviewer submits, cancels, or the session ends:

    npx -y @obversa/surface-diff@0 <selected args>

Pick the arguments from what was asked for: no mode flag reviews the working
tree; `--staged` only when the staged changes were requested; `--range A..B`
for a ref range. `--cwd <dir>` runs against another repository directory;
`--no-open` prints the URL on stderr instead of placing the surface.

## Handle the result

Read only the JSON between `<<<REVIEW_RESULT_V1>>>` and
`<<<END_REVIEW_RESULT_V1>>>` on stdout.

- `completed`: `payload.decision` is `approved` (no annotations) or
  `changes-requested` (one or more). Apply each annotation at its anchor
  (`target`, `side`, `position`).
- `cancelled`, `timed_out`, `interrupted`, `error`: make no change and report
  the status and `detail`.
- No frame at all (the command exited before printing one, for example because
  the package could not be fetched or resolved): treat it as `error`. Report
  the last lines of stderr, make no change, and do not retry with a different
  version.
- `surface.package` and `surface.version` name the package and the resolved
  version that ran. Report them with the outcome.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.