matthew-a-carr/review-implementation
Repo-aware review of an implementation PR (the `ai:done` PR) against the SPEC it implements, the constitution, the ADRs, and the doc-staleness rules. Use when a routine fires on a PR labelled `ai:done`, when a human says "review impl PR #NNN" / "review the implementation for SPEC-NNN", or as a self-review step inside `implement-spec` before the PR is opened. Read-only — produces a structured report and never edits code or merges.
85
90%
Does it follow best practices?
Impact
69%
1.06xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
task.mdevals/scenario-2/
Implementation PR Review: Search Feature
Problem/Feature Description
A developer on your team has submitted a pull request implementing SPEC-071, which adds a full-text search capability for travel bookings. The feature includes a new domain query object, a search use-case, a repository method, and API endpoint.
The developer claims the PR is complete and all tests pass. However, the team lead has flagged some general concerns about the completeness of the submission and has asked for a thorough review before it is merged.
You have been asked to review the PR before it is merged, using the files provided in inputs/. Pay particular attention to whether the test suite is genuinely green and complete, and whether the documentation is up to date.
Output Specification
Write your full review to review-report.md in your working directory.
The source material is in inputs/:
inputs/SPEC-071-search.md— the SPECinputs/impl-notes-071.md— the implementation notesinputs/diff.patch— the code changes
Include a verdict and categorised findings in your report.