# Code Review

> Code review of a diff, branch, PR, commit range, or working tree against standards and agreed requirements.

- Skill: `muhammedalkhudiry/code-review` (Agent Skill)
- Install (CLI): `npx skillmds@latest add muhammedalkhudiry/code-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/muhammedalkhudiry/code-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: MuhammedAlkhudiry (https://skillmd.com/u/muhammedalkhudiry)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/muhammedalkhudiry/code-review

---


Review along two independent axes:

- `Standards`: defects, maintainability risks, hidden coupling, misleading structure, and documented convention violations.
- `Spec`: missing, partial, incorrect, ambiguous, or unrequested behavior relative to the agreed requirements.

## Workflow

1. Use the fixed point named by the user. Otherwise infer the base branch or use the current staged and unstaged diff; ask only when the review
   surface cannot be determined safely.
2. Resolve the comparison and confirm it has a non-empty diff. Use `git diff <fixed-point>...HEAD` for branch-style comparisons.
3. Resolve the spec from the user's request or linked issue, PRD, plan, PR, or project documentation. If none exists, skip that axis and report
   `No spec available`.
4. Read applicable repository instructions and conventions, then review Standards and Spec independently. Documented project standards override
   general judgment; do not report issues already enforced by tooling unless the change bypasses that tooling.
5. Ground every finding in a concrete file or hunk. Keep the axes separate and report counts and the worst finding for each.

## Finding format

Severity: `CRITICAL` is exploitable, destructive, or release-blocking; `HIGH` is serious; `MEDIUM` is contained; `LOW` is minor. Every finding must
name the problem, location, concrete impact, and actionable fix:

```md
- **<CRITICAL | HIGH | MEDIUM | LOW>: <problem>** (`<file>:<line>`)
  - **Impact:** <impact>
  - **Fix:** <fix>
```

## Output

```md
## Standards

<findings in the required format, or "No findings">

## Spec

<findings in the required format, "No findings", or "No spec available">

Summary: Standards <count>; Spec <count>. Worst Standards issue: <item or none>. Worst Spec issue: <item or none>.
```