← ClaudeAtlas

code-reviewlisted

Review code changes for bugs, security holes and regressions before they merge. Use when the user says "review my changes", "review this PR", "check this diff", "is this safe to merge", or names a branch, commit or files to look over.
Kuan-AI-com/agent-skills · ★ 0 · Code & Development · score 72
Install: claude install-skill Kuan-AI-com/agent-skills
# Code review The goal is a short list of real problems, each one verified against the code. A review with two true findings beats one with ten guesses. ## 1. Get the exact change - Working tree: `git status` first, then `git diff HEAD` (staged + unstaged). Untracked files do not show in a diff: read them. - Branch: find the base, do not assume `main`. Use `git symbolic-ref refs/remotes/origin/HEAD` or ask. Diff with `git diff <base>...HEAD` (three dots = since the merge base). - PR number: `gh pr diff <n>` if `gh` is available; otherwise ask for the branch. - If the diff is over ~1500 lines, say so and review the riskiest files first (auth, payments, data writes, migrations, concurrency), listing what you skipped. ## 2. Understand intent Read the commit messages or PR text. A bug is a gap between what the change is meant to do and what it does. If the intent is unclear, state your assumption. ## 3. Read beyond the hunk For every changed function, open the full function and the code it calls. For every changed signature, return type, default value, config key or DB column, search for all usages (`git grep -n <name>`) and check each caller still works. Most real bugs live in code the diff did not touch. ## 4. Look for these, in this order 1. Wrong behavior: inverted conditions, wrong variable, missing `await`, early return skipping cleanup, error swallowed, partial writes without a transaction. 2. Security: untrusted input reaching SQL, shell, HTML, file paths, redire