Awesome Reviewers checks + prompts

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.

V1032 technique
tactic Code review
not detectable from CI configuration

Sub-techniques

2

IDNameDescription
V1032.001Change summaryGenerate a description and per-file walkthrough of the diff.
V1032.002Topic groupingGroup changed files by topic and rate each topic's importance.

Craft 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.

Reverse engineer it

Signs that a codebase already runs this technique, and where to read how it is configured.

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

Open-source packages

4