# Mass Code Review > Reviews a pull request or a local diff for correctness bugs, missing tests and unsafe changes, and reports findings with file and line. Use when "review this PR", "review my changes" or "look for bugs in this diff". Do NOT use for writing the PR description (use mass-pr-description) or for a security-only audit of a skill (use mass-security-checklist). - Skill: `maiconsouza89/mass-code-review` (Agent Skill) - Install (CLI): `npx skillmds@latest add maiconsouza89/mass-code-review` - Raw SKILL.md: https://api.skillmd.com/api/skills/maiconsouza89/mass-code-review/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Security - License: CC-BY-4.0 - Author: maiconsouza89 (https://skillmd.com/u/maiconsouza89) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/maiconsouza89/mass-code-review --- # Code review Find what would break, not what you would have written differently. ## Steps 1. Get the diff. For a PR: `gh pr diff ` and `gh pr view --json title,body`. For local work: `git diff ...HEAD`. 2. Read the linked issue or the PR summary first so the review judges the change against its own goal. 3. Walk the diff file by file and ask, for each hunk: what input makes this wrong, what happens on the error path, what test would have caught it. 4. Check the tests: does a new branch have an assertion that fails without the change? A test that only exercises the happy path is a finding. 5. Check the edges of the change: callers of a renamed or re-typed symbol, migrations against existing data, workflows that run the changed command. ## Report One finding per line, most severe first: ` : - - ` Severities: `bug` (wrong result or crash), `risk` (unsafe under a plausible input), `test` (missing or weak coverage), `nit` (style, only if it hides a bug). End with one line: `No blocking findings.` or `Blocking: .` Do not post to GitHub unless the user asked; when asked, use `gh pr review` with the findings as the body.