Reviewing Changes

Review an actual candidate against the user's acceptance and scope, then carry findings through fixes, affected checks and rereview. Use before claiming a substantive change complete or accepting a worker's implementation.

33 stars 4 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add okgrit/done-is-a-claim

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add okgrit/done-is-a-claim --skill reviewing-changes
Manual install
git clone --depth 1 https://github.com/okgrit/done-is-a-claim.git /tmp/done-is-a-claim
mkdir -p ~/.claude/skills
cp -r /tmp/done-is-a-claim/skills/reviewing-changes ~/.claude/skills/reviewing-changes

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Reviewing changes

Review the delivered candidate, not the author's confidence or task status.
Support findings with the user's contract, the actual diff and observable
behavior. A review is useful only to the extent its inspected scope is clear.

## Establish the review inputs

1. Read the user outcome, acceptance commands, preserved behavior and scoped
   file ownership. Confirm the assigned checkout and applicable instructions.
2. Identify base and candidate revision, plus uncommitted and untracked inputs.
   Inspect the diff and affected artifacts directly. Verify referenced paths.
3. Read existing check output, command, exit status and input identity. Treat
   author and worker reports as leads; do not turn a result label into evidence.
4. State the review mode. Use an independent reviewer when permitted and
   available with a bounded brief and evidence. Otherwise perform self-review
   explicitly, naming the loss of independence without pretending another agent ran.

## Look for consequential defects

Evaluate the candidate against the original outcome, compatibility, edge cases
and relevant callers. Confirm checks can distinguish the intended behavior from
a plausible failure. A constant assertion, file existence or successful response
alone may not test the boundary the user cares about.

Inspect all affected call sites for a defect class, not only the example fixed.
Check that generated artifacts, consumers or rendered output work where those
Read the full skill on GitHub

Details

Skill name
reviewing-changes
Path
skills/reviewing-changes/SKILL.md
License
Apache-2.0
Repo updated
25 October 2026

FAQ

What does the Reviewing Changes skill do?

Review an actual candidate against the user's acceptance and scope, then carry findings through fixes, affected checks and rereview. Use before claiming a substantive change complete or accepting a worker's implementation.

How do I install the Reviewing Changes skill?

Claude Code plugin: /plugin marketplace add okgrit/done-is-a-claim. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Reviewing Changes popular?

It lives in okgrit/done-is-a-claim, which has 33 GitHub stars and 4 forks, and is included in 1 curated skill list.

Related skills

Acceptance Design

33

okgrit/done-is-a-claim

Define executable acceptance for a bounded task before work or dispatch. Use when writing a worker brief, selecting success checks, or repairing an acceptance contract that cannot test the intended outcome.

Testing & QAIn 1 list

Checking Delivery

33

okgrit/done-is-a-claim

Verify an artifact at its actual delivery destination and distinguish send attempts, acknowledgements, publication and consumer checks. Use when reporting a file, message, export or deployment as delivered; creating a local draft alone does not imply delivery.

DevOps & CloudIn 1 list

Collecting Worker Results

33

okgrit/done-is-a-claim

Inspect a stopped worker's returned work and evidence before accepting it, retrying it or handing it to an integration owner. Use when a worker finishes, records disagree, or a green result has no visible change. Collection does not authorize merging.

OtherIn 1 list

Tracking Plan Audit

48

amplitude/mcp-marketplace

Use when auditing Amplitude tracking plans for safe deletion candidates among stale, duplicate, orphaned, cross-app, retired, high-volume, generated-client, never-ingested, or deleted-but-still-emitted events and event properties.

Other12

Release Process

45

Azure-Samples/agent-skills-dotnet-demo

Step-by-step release checklist for Squad — prevents v0.8.22-style disasters

Other11

Weekly Brief

48

amplitude/mcp-marketplace

Delivers a weekly briefing summarizing the most important trends, wins, and risks across your Amplitude instance. Use when the user asks for a "weekly review", "weekly summary", "week in review", "what happened this week", or wants a recap of the past 7 days to share with their team or leadership.

Other12

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.