Explore the guides +
Skills/review-changes
Companion / SKILL GUIDE

review-changes

Review the diff for defects you can point to and explain.

I want a review to tell me what can fail, where it fails, and why. This skill reads the full change and its callers, checks the acceptance criteria, and keeps findings grounded in concrete failure scenarios.

When I’d use it

Use it before merging or handing off a change, especially for a risky contract or permission change. It can review a local diff, a branch, a commit range, or a pull request.

Before you start

Give it the base ref or change and the intended behavior. An evidence record can help explain what was tested, but it is not proof that the implementation is correct.

Install it. Then give it a task.

Run this in your project’s terminal. Choose your coding agent in the installer, then start a new agent session if it needs one to discover the skill.

TERMINAL
$ npx skills add akdevsaha-dev/factory-skills --skill review-changes

Once installed, send a prompt like the ones below to your agent. These are example requests to adapt to your own project, not terminal commands or recorded results.

If slash commands aren’t available in your agent, write “Use the review-changes skill to…” and describe the same task.

New to skills? Start with the installation walkthrough

What happens next

  1. Reads the full diff, surrounding code, and affected callers.
  2. Checks every acceptance criterion on success and failure paths.
  3. Investigates correctness, security, contracts, tests, and maintainability.
  4. Confirms and ranks findings, then gives a verdict.

A few ways to ask

5 examples

Copy the one closest to your task. Replace names, paths, dates, and refs with ones that exist in your project.

01

Review current work

SEND TO YOUR AGENT
› /review-changes review the current changes against the CSV export request. Check that the export matches the filtered list and handles escaping correctly.

Give the reviewer the behavior to assess, not just an implementation summary.

02

Review a branch

SEND TO YOUR AGENT
› /review-changes review this branch against main. Focus on confirmed failures and include file locations and reproduction scenarios.

The base needs to exist locally.

03

Check a permission boundary

SEND TO YOUR AGENT
› /review-changes review the new organization membership checks. Trace direct API calls, cross-organization resource IDs, and role changes.

The review reports findings; it does not change access or patch the product code.

04

Compare a commit range

SEND TO YOUR AGENT
› /review-changes review the change from BASE_REF to HEAD against the acceptance criteria in the task.

Replace BASE_REF with the actual commit or branch you want compared.

05

Review after a fix

SEND TO YOUR AGENT
› /review-changes re-review the fix for the duplicate import finding. Confirm the earlier issue is resolved and inspect the paths changed by the fix.

A re-review should concentrate on the fix and affected code, not repeat the same unchanged review.

What to look for in the result

Evidence-backed findings with severity, locations, and failure scenarios, plus a verdict for the acceptance criteria. If nothing survives confirmation, it should say so plainly.

A thing worth watching

A review with no findings is useful evidence, not a guarantee of zero bugs. Keep taste preferences separate from defects and from the project’s documented conventions.

Use it with

Based on the repository’s skill instructions.Read the source
PUT IT INTO PRACTICE

Build a workflow you can repeat.

Follow the step-by-step guide to working with agents.

Explore Learn