Team memory

Vetoo reviews your code better the longer it works on your code. Two things drive this: your votes and comments on findings, and a daily job that turns scattered feedback into lasting patterns.

Vote findings up or down

Vote each finding up or down in the request. A downvote tells Vetoo that the finding did not belong. Vetoo then holds back that kind of finding in later reviews of the same repository. Findings your team does not want therefore disappear from later reviews. An upvote reinforces the findings you want to keep.

Consolidation

One day of votes and comments carries little signal on its own. A daily job consolidates those votes and comments. A signal that recurs becomes a lasting pattern for the repository, and Vetoo drops one-off noise. The pattern then shapes later reviews of that repository. Your feedback therefore steers the review, not a settings page you fill in at the start.

Why a rules file alone is not enough

You cannot write down every preference in advance, and a codebase changes over time. A vote keeps the calibration next to the work. You respond to a real finding on a real change, and the next review moves closer to what you want. Repeated downvotes on one kind of finding remove it from later reviews of that repository.