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
This repository has one existing GitHub Actions workflow, .github/workflows/ci.yml,
which runs the test suite. The team wants automated pull-request review added
alongside it, using the supported Tessl Code Review Action, tesslio/code-review-action.
The team has already decided how they want it to behave, so no questions need to be asked:
Follow this repository's existing conventions for workflow file naming and for
pinning third-party actions. The Tessl API token is supplied to the workflow as a
repository secret named TESSL_TOKEN.
The team is adopting release v1.4.0 of the Action, whose commit SHA is
7c2f9a1e4b8d63057e9a1c4b8d63f0572a9e1c4b. Pin that full SHA, and name the
release in your summary. Do not pin a tag, a branch, main, or canary, and do
not leave a placeholder in the file.
Produce the following files:
.github/workflows/, invoking
tesslio/code-review-action and nothing else. Do not copy or reimplement any review,
checkout, CLI-setup, or review-publication logic into the workflow.summary.md at the root of the workspace, documenting the cadence and blocking
contract that was installed, the repository secret the workflow needs, the
permissions it grants and why, and how to update or remove the setup later.Leave .github/workflows/ci.yml unchanged.