code-review

Code Review

Purpose

This skill reviews completed implementation before it becomes part of the project's engineering history.

The objective is to verify that the implementation:

• satisfies the approved implementation plan;
• follows the documented architecture;
• follows the approved engineering conventions;
• preserves repository consistency;
• introduces no unintended scope.

Code Review is the final quality gate before recording project progress.

---

Lifecycle Stage

Plan Implementation
        ↓
Code Review
        ↓
Progress Update

Code Review validates completed implementation.

It does not redesign the project.

---

Role

Primary role:

Review Agent

---

When to Use

Use this skill when:

• implementation has been completed;
• validation has been performed;
• documentation has been updated;
• implementation is ready for acceptance.

Perform Code Review before committing completed work to project history.

---

Inputs

Required:

• approved implementation plan;
• implementation changes;
• PROJECT.md;
• ROADMAP.md;
• ARCHITECTURE.md;
• ENGINEERING.md.

Additional references:

• ADRs;
• completed plans;
• current repository state.

---

Outputs

Produce one review outcome:

• Approved
• Approved with Minor Suggestions
• Changes Requested

Every requested change should include clear reasoning and evidence.

---

Procedure

Step 1 — Understand the Intent

Review:

• implementation plan;
• implementation scope;
• acceptance criteria;
• validation requirements.

Understand the approved engineering intent before reviewing code.

---

Step 2 — Review the Implementation

Evaluate:

• correctness;
• completeness;
• maintainability;
• readability;
• consistency.

Look for unintended behavior and incomplete implementation.

---

Step 3 — Verify Scope Compliance

Confirm that:

• only approved functionality has been implemented;
• no undocumented features have been introduced;
• no unrelated refactoring has occurred;
• implementation remains within approved scope.