Code review

Run a structured self-review pass on changed files before opening a pull requestFrom its SKILL.md

Install

npx -y skills add claudifytech/claude-code-skills-starter --skill code-review

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.

1.5 KB, 311 tokens by cl100k_base, as published. Nobody here has run it

Review the current changes the way a careful reviewer would, and report findings ranked by severity.

Before opening a pull request, or when the user asks for a review of recent changes.

Run git diff (or git diff main...HEAD) to see what changed. Read the full changed files, not just the diff hunks, so you have context.
Check each of these and note any issue with a file and line reference:
- Correctness: logic errors, off-by-one mistakes, wrong conditionals, unhandled null or empty cases.
- Edge cases: empty input, very large input, concurrent calls, failure of an external call.
- Security: unvalidated input, secrets committed in code, injection risks, missing authorization checks.
- Conventions: does the change match the existing patterns and style of the surrounding code?
- Tests: is the new behavior covered? Are existing tests still valid?
- Clarity: misleading names, dead code, comments that no longer match the code.
Rank findings as blocking, should-fix, or nit. Lead with blocking.
For each finding give a one-line fix suggestion, not just the problem.
If you find nothing significant, say so plainly rather than inventing issues.

A short summary line, then the findings grouped by severity, each as file:line plus the issue and the suggested fix.

Read from the repository

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