domains / families / software-engineering / code-review

code-review

combined

Review source files changed during a phase for bugs, security issues, and code quality problems Review changed code for naming, stale references, unnecessary complexity, and comment quality. Use after completing implementation work, before committing, or when the user asks to review or audit code.

When to use

• Most review output is noise: a list of things that *look* wrong, unranked, unrefuted, and impossible to act on. This skill produces the opposite — a small number of findings, each with a required behaviour, a feasible trigger, a concrete c…

When not to use

• Tasks not involving code review or auditing
• Implementation work before review is requested

Skill page

Conflict

The four skills define fundamentally different review engines. mattpocock/skills uses a two-axis (Standards vs Spec) parallel sub-agent model anchored to a git diff. phuryn/pm-skills uses a defect-focused 'agreement engine' that forces violating executions to prove bugs. dzhng/skills is a heuristic checklist for code hygiene (naming, comments, complexity). davepoon/buildwithclaude is a thin dispatcher for a phase-based workflow that spawns a specific agent. Because they disagree on the core methodology (diff-based vs defect-proving vs heuristic vs phase-based) and each contains unique steps (e.g., Fowler smells, violating execution construction, stale reference grepping, phase validation), crowning one would hide the others' distinct approaches.