Review Pattern Mining

Use this when handling PR review feedback and you want to reduce repeated follow-up review on the same branch.

Goal

Treat each review comment as a chance to infer a broader rule, then apply that rule across the rest of the current diff where it clearly fits.

Core Rules

• Extract the underlying rule, not just the literal line edit.
• Fix the same pattern everywhere in the current diff when the rule is objective and low-ambiguity.
• Do not cargo-cult a reviewer suggestion across unrelated code.
• If the feedback is architectural or taste-heavy, decide once and either:
  • refactor intentionally across the relevant seam, or
  • prepare a concise pushback draft with reasoning.
• Prefer one coherent follow-up refactor over many tiny copy-paste fixes.
• Keep the blast radius proportional to confidence.
• If a suggested sweep depends on another PR or pending upstream change, call that out explicitly instead of guessing.