Individual skill

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.

skills/reviewing-changes/SKILL.md

Read pinned source

Source commit 14c75a97ccbcca4c11daca25a93c8f0da5ad70d1

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 33
Repository last updated: Oct 25, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agents-md Repository topic
ai-agents Repository topic
claude-code Repository topic
claude-md Repository topic
codex Repository topic
coding-agents Repository topic
llm Repository topic
testing Repository topic
verification Repository topic
agent-skills Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 4,691 bytes

Read excerpt


# 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.