Your team has rules. They're buried in PRs.
Compile recurring, accepted review feedback into a rulebook for Cursor, Claude Code and CodeRabbit. Evidence included.
$ node dist/cli.js --repo acme/web --months 6
✓ scanned 84 merged PRs
✓ read 1,247 human comments
✓ found 7 repeated rules
→ .cursor/rules/team-review.mdc
✓ scanned 84 merged PRs
✓ read 1,247 human comments
✓ found 7 repeated rules
→ .cursor/rules/team-review.mdc
01
Scan locally
Read-only GitHub access. Code and comments never pass through our server because there is no server.
02
Find the pattern
Cluster repeated human feedback and rank it using code-change signals, reviewers and frequency.
03
Ship the rulebook
Export reviewed rules to the coding agents and reviewers your team already uses.
Three undocumented rules in ten minutes.
That is the bar. If your team's PR history cannot produce useful rules, the tool should say so.
Avoid network calls in React components.
11 occurrences · 9 accepted-change signals · 91% confidence
Examples link back to the exact review comments. A human approves before enforcement.