tessl/code-review-setup
Install Tessl Code Review into a GitHub repository. Inspects the repository's existing workflows and any Code Review caller already present, asks the two setup questions (when reviews run, and whether findings block the merge), then writes or updates a thin caller workflow that invokes the Tessl Code Review Action. Use when someone wants to add, set up, enable, configure, update, or remove Tessl Code Review, AI code review, or automated pull-request review in a repository, or asks to switch it between advisory and gate mode.
94
92%
Does it follow best practices?
Impact
97%
1.40xAverage score across 5 eval scenarios
Low
Low-risk findings worth noting
task.mdevals/scenario-3/
Move the existing Code Review setup to every-commit reviews
Problem Description
This repository already runs Tessl Code Review. The caller workflow lives at
.github/workflows/tessl-code-review.yml and currently reviews a pull request
once when it becomes ready, plus any round requested by a comment mentioning
@tessl-code-review.
The team now wants a review on every push to a pull-request branch, with the in-flight review superseded when a newer commit lands. Everything else about their setup stays as it is: still advisory, still the standard profile, still their self-hosted runner, their 45-minute timeout, their job name, and the step that writes the review status into the run summary.
At the same time, pin the Action to the revision from the release they are
adopting: 4c8e1d0a9b7f6e5d4c3b2a1908f7e6d5c4b3a291.
Output Specification
Update the repository in place:
.github/workflows/tessl-code-review.ymlreflects the new cadence and the new pinned revision, with the team's own settings preserved.summary.mdat the root of the workspace, listing exactly what changed in the workflow and what was deliberately left alone, and explaining why superseding a running review is safe.
Do not add a second workflow that calls the Action.