Awesome Reviewers

Verification · Code review

Change intent extraction

States what the change is meant to do, from title, description, commits and linked ticket, so every later check can ask whether a finding is in scope.

Sub-techniques

  • Change summary V1032.001

    Generate a description and per-file walkthrough of the diff.

  • Topic grouping V1032.002

    Group changed files by topic and rate each topic's importance.

How to build it

  1. Feed title, body, commit messages and linked ticket to a model with a structured output schema.
  2. Use a structural diff so moved code is not reported as new.
  3. Store the intent with the review so findings can be checked against it.

Signals in a repository

  • A PR description bot or a generated summary section in PR bodies.