Review changes

Skill prathakmalik/agent-standards-kit/skills/review-changes

Reviews a set of code changes (a diff, a branch, or staged/uncommitted work) for correctness, edge cases, security, performance, and consistency with the repo's conventions. Use when the user asks to review changes, review a PR, check a diff, or sanity-check work before committing. Trigger phrases: "review my changes", "review this PR", "check this diff before I commit".From its SKILL.md

Install

npx -y skills add prathakmalik/agent-standards-kit --skill review-changes

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 313 tokens by cl100k_base, as published. Nobody here has run it

review-changes

A rigorous, constructive review of proposed changes. Prioritize code health over politeness, but be specific and actionable.

When to use

Before committing or opening a PR.
When asked to review a diff, branch, or file set.

What to inspect

Logic & edge cases: off-by-one, null/undefined, empty collections, error paths, race conditions.
Security: unsanitized input, injection, secrets in code, missing authz checks.
Performance: accidental O(n^2), N+1 queries, unnecessary work in hot paths.
Consistency: does it follow existing patterns in this repo? (Check neighboring files.)
DRY/clarity: duplication that should be extracted; names that mislead.

How to respond

Structure the review as:

Summary — 1-2 sentences on the impact of the change.
Blocking issues — bugs or security flaws that must be fixed.
Suggestions — refactors, perf, style (non-blocking).
Positives — call out genuinely good solutions.

Rules

Verify call sites when a signature changes — a local edit can break a distant caller.
Cite exact files/lines. Prefer a concrete fix over a vague concern.
If the diff is large, review by theme, not file-by-file noise.
Don't invent problems to seem thorough. "Looks good, here's why" is a valid result.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.