W Review

by blockmatic7e05e2abd052dc6b526e8a28e36d102d42bfd635No license1 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 6 days ago

Review a change for evidenced defects and risks without editing it.

AI-generated overview

Reviews a code change read-only, validating suspected defects with evidence and reporting findings by impact.

What it does: Reviews a specified diff, branch, pull request, or working tree against its intended behavior while remaining read-only unless fixes are requested. It reads tests to see which claims are exercised, checks in-scope review dimensions (including docs/README when behavior changed), and may spawn 2-3 read-only explorers that split those dimensions. Suspected defects must be validated with a concrete execution path, failing case, or source evidence, and findings are ordered by impact with file/line, trigger, consequence, and the smallest useful remedy.
When to use it: Use when a code change needs review for evidenced defects and risks before merging. It fits situations where the reviewer should stay read-only and challenge verification claims rather than approve the change.
Requirements: Instructions only; no scripts are shipped. It relies on access to the change under review (diff, branch, PR, or working tree), its tests, and the referenced references/review-dimensions.md file.

Use the specified diff, branch, PR, or working tree and its intended behavior. Remain read-only unless fixes are also requested.

Understand the trigger and expected result before judging the implementation. Read tests to learn which claims are actually exercised.
Check the in-scope review dimensions [blocked], including docs/README when behavior changed. Spawn 2–3 read-only explorers that split those dimensions. Concentrate on changed behavior, callers, and failure paths. Skip dimensions that are out of scope and say so.
Validate suspected defects with a concrete execution path, failing case, or source evidence. Do not invent timings or vulnerabilities from appearances.
Challenge verification claims. Order findings by impact with file/line, trigger, consequence, and smallest useful remedy. An inspection is not proof that tests passed and is not approval to merge.

Source and attribution

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.