tessl/code-review-lens-creator
Author a review lens for Tessl Code Review: the reviewer skill that decides what `tessl code review` and the Tessl Code Review Action look for in a diff. Frames the review question and the bar a finding has to clear, drafts the lens, validates it by running it against changes that should and should not trip it, backtests it against pull requests that already carry review feedback, then packages it as a pinned registry ref a workflow can select. Use when someone wants their code review to catch something it misses, to stop flagging something it should not, or to write, fork, tune, or debug a code review lens. Not for `tessl review` rubrics, which score skill quality rather than code.
90
97%
Does it follow best practices?
Impact
96%
1.29xAverage score across 2 eval scenarios
Passed
No findings from the security scan
task.mdevals/scenario-1/
Our new review lens is too noisy to turn on
Problem Description
We wrote an observability lens and backtested it over 12 pull requests before adopting it. The results are in backtest-results.md. It found real things, but 19 of its 31 findings were noise, it missed a whole family of problems that the human reviewers caught every time, and four of its findings never made it to an inline comment.
Nobody will read a review with that hit rate, so the lens is not going on until the numbers are better.
The lens is at review-lenses/review-observability/SKILL.md.
Output Specification
- Revise
review-lenses/review-observability/SKILL.mdin place. - Write
tuning-notes.mdexplaining each change you made, which category of backtest result it addresses, and what has to happen before we adopt the lens.
Do not create a second lens.