Engineering Flow
中文
← Back to workflows

WORKFLOW 04 / 05

Review

Review a fixed diff or branch and report actionable findings.

STRICTLY READ-ONLY

Core idea

Evidence-backed findings, ordered by impact. Report only — the review never touches the code.

How it runs

  1. 01
    Fix the comparison

    Pin the review target: a diff, a branch merge-base, or current uncommitted work. A bad reference fails loudly instead of reviewing the wrong change.

  2. 02
    Recover the intent

    Read the review request, project rules, the originating requirement, and tests — learn what the change was supposed to do.

  3. 03
    Review by axes

    Check eight axes independently: requirements, correctness, safety, design, readability, tests, documentation, and scope.

  4. 04
    Report findings

    Order by impact. Every finding cites its location, evidence, and the smallest credible fix. Not a single file is edited.

Key mechanisms

Fixed comparison point

The review target is frozen at an explicit reference. A missing reference or empty scope fails clearly — no reviewing a moving target.

Eight independent axes

Requirements, correctness, safety, design, readability, tests, documentation, and scope are checked one by one, never blurred together.

Strictly read-only

No edits, no commits, no pushes. Findings arrive ranked by severity with evidence; fixing is someone else’s job.