Reviews and findings

A review starts when you press Build done. Plyloft takes a snapshot of the Builder’s work, runs your checks, and hands the snapshot to the Challenger.

What a review produces

• A verdict: nothing blocking or changes requested.
• Findings, each with a priority and, when it names a line, a place in the diff. A finding reads like F1 · P1 — maxAge is in milliseconds in Express.
• The skills it followed, shown as chips: Followed review-rules.

Findings on the diff

See the result (beside Checks) opens The result; its See the diff opens The diff, beside the result on a wide window. Every finding with a line sits in a box under that line, with its state (Open, Still open, Closed) and its history, for example Raised in round 1 · closed in round 2. When the line changed since the review, it says This line changed since the review., and where it was: It was line 10. Low-priority and non-blocking findings start collapsed.

Above the diff, the round switch All · Round 1 · Round 2 shows the findings of one round: Findings raised or closed in round 1. With more than four rounds it is a menu.

Note

Line comments are yours; findings are the Challenger’s. Click a line to comment on it: your comments go to the Builder, never to GitHub.

Serious issues

A P1 finding is a serious issue. The Inbox says 1 serious issue · changes requested, and while the review asks for changes the card’s result names it first, for example Serious issue · maxAge is in milliseconds in Express with its place, src/auth/session.ts:42.

Rounds

1. The Challenger requests changes. Its findings go straight to the Builder’s session.
2. The Builder fixes them, or explains why it disagrees.
3. You press Build done again. A new snapshot, new checks, a new review: round 2.
4. Repeat until the review finds nothing blocking.

The card’s Activity keeps every round, for example Round 2 · Codex · nothing blocking · 1 closed. Each round keeps its own findings: See its findings shows exactly those.

When the Builder disagrees

The Builder can push back on a finding with a reason. You decide: Accept the Builder’s pushback in the Now box, or tell it to fix the finding anyway.

Correcting the result yourself

If the result is wrong in a way the review missed, use Not right — tell them what’s wrong. Your words go to the Builder. After the card is settled, the Challenger may turn your correction into a proposal for a skill, so later reviews catch it. See Skills and the Library.