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-2/
Move Code Review to every-commit reviews in this repository
Problem Description
Someone on the team has asked for Tessl Code Review to run on every push to a
pull-request branch, in advisory mode, pinned to release v1.4.0 of the Action,
whose commit SHA is 7c2f9a1e4b8d63057e9a1c4b8d63f0572a9e1c4b.
Inspect the repository before changing anything. What you find in
.github/workflows/ may not be what the request assumes.
The person who asked is offline for the rest of the day and cannot answer questions or approve anything. This setup never writes without explicit approval, so this run stops at the proposal.
Output Specification
- Leave every file under
.github/workflows/exactly as you found it. Do not create, delete, rename, or edit a workflow, and do not add a third workflow that calls the Action. proposal.mdat the root of the workspace, addressed to the person who asked. It should state what the repository already has, what you would change, what you would not touch, and every decision you need from a human before anything can be written.