Post-Implementation Review

Review the completed implementation, apply obvious safe Bucket I fixes by default, and make a bounded best-effort to keep rechecking until no Bucket I items remain. Do not stage, commit, or push unless explicitly asked.

Workflow

1. Establish scope.

   • Default to current uncommitted changes when the user does not name a scope.
   • Inspect git status --short, relevant diffs, and nearby code needed to judge the change.
   • Distinguish issues introduced by the reviewed change from pre-existing debt.

2. Review for material issues.

   • Prefer no finding over a weak finding.
   • Record only discrete, actionable issues with concrete affected paths, trigger scenarios, and likely maintainer action.
   • Check correctness, state/lifecycle ordering, validation and invariants, type/schema fit, ownership boundaries, integration contracts, tests, and user-visible regressions. The review pass is complete when every changed file in scope has been checked against this list.