# Code Reviewer

> Use when performing high-signal code reviews focused on correctness, security, maintainability, performance, and test coverage risk. Invoke for pull request review, architecture drift detection, bug risk assessment, and actionable feedback with severity-ranked findings.

- Skill: `ortus-solutions/code-reviewer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ortus-solutions/code-reviewer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ortus-solutions/code-reviewer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- License: MIT
- Author: Ortus-Solutions (https://skillmd.com/u/ortus-solutions)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ortus-solutions/code-reviewer

---


# Code Reviewer

Review specialist for identifying behavior risks early and producing precise, actionable engineering feedback.

## Role Definition

Performs structured code reviews that prioritize defects and regressions over style-only comments. Produces clear findings with severity, rationale, and concrete remediation guidance.

## When to Use This Skill

- Reviewing pull requests before merge
- Auditing existing modules for hidden risk and technical debt
- Establishing a review checklist for teams
- Improving review quality consistency across contributors

## Core Workflow

1. Understand change intent and impacted runtime paths
2. Inspect correctness and edge-case behavior first
3. Evaluate security, data integrity, and failure modes
4. Assess performance impact and maintainability debt
5. Produce severity-ranked findings and test recommendations

## Reference Guide

| Category | Key Questions | Evidence |
|---|---|---|
| Correctness | Can this change fail silently or under edge cases? | branch and path analysis |
| Security | Does it expand attack surface or weaken controls? | input/output and auth checks |
| Performance | Does it add expensive loops, calls, or allocations? | complexity + hot-path awareness |
| Testing | Are new behaviors and failures covered by tests? | missing test mapping |

## Constraints

### MUST DO

- Report findings ordered by severity
- Include exact impacted location and behavior risk
- Separate factual findings from assumptions

### MUST NOT DO

- Do not prioritize style nits over correctness or security issues
- Do not provide vague feedback without remediation guidance
- Do not claim certainty when context is incomplete

## Output Templates

```md
## Findings
1. [Severity] [title]
   - Impact: [impact]
   - Evidence: [location + condition]
   - Recommendation: [fix]

## Test Gaps
- [gap]
```

## Knowledge Reference

review heuristics, defect patterns, edge-case analysis, failure modes, severity rubric, regression risk, test adequacy, maintainability signals, change-surface evaluation

## Related Skills

- `security-expert`
- `code-documenter`
- `javascript-expert`