tessl-carnival

Add a new game to the Tessl Carnival midway, following the water cannon pattern and the house rules. Use when asked to build, add or create a carnival game or booth, such as ring toss, whack-a-mole, hook a duck or high striker.

Change or extend a Tessl factory that is already set up on this repository, and suggest what to add next. Use when someone wants to let a teammate start runs, change the model an automation uses, change what an automation does, change how Code Review behaves, stop or remove an automation, update the setup hook, change what the cloud environment can access, add another automation, set up Improve development so the factory learns from its mistakes, act on its findings, or asks what they should add to their factory.

Run a branch's setup hook on a Tessl cloud machine and report its output and what the machine then has, so factory setup can confirm the hook works in the cloud before it goes live. Use when factory setup launches a cloud run to check a setup hook.

Find docs and agent instructions in the carnival that no longer match the code, and file one GitHub issue per stale doc. Use when running the doc gardening maintenance loop, or when asked to check whether the README, AGENTS.md, a game's README or a skill is out of date. Files issues only; never changes code or docs.

Set up, explain, or change a Tessl factory on a repository: agents that act on events in the repo, such as triaging new tickets, shipping tickets as pull requests, answering reviews and fixing checks on those pull requests, reviewing code, or running a job on a schedule. Use when someone wants Tessl agents to do work in their repo, asks what a factory is or what theirs does, or wants to add to, change, or customize it.

Prepare an existing repository so Tessl agents and Tessl Code Review work well in it: better agent context, verifiers, Code Review lenses, and lint rules drawn from how the team already works. Use when someone wants agents to make fewer mistakes in their repo, wants to prepare or improve their repo for agents, or wants to turn recurring review feedback into checks.

Read recent code review on this repository's pull requests, find the mistakes reviewers keep catching, and file a GitHub issue proposing a rule so agents get it right next time. Use when running the rule mining maintenance loop, or when asked what the agent keeps getting wrong in review. Files issues only; never changes code or docs.

Turn on the GitHub features a fork of the carnival needs (Issues, Actions and GitHub Pages) using the GitHub CLI, then deploy the carnival and share its link. Use when someone asks to set up their fork, turn on issues or Pages, get a shareable link to their carnival, or when the Issues tab, CI checks or the Pages deploy are missing on a fork.

Find weak, dead or misleading tests in the carnival and file a GitHub issue for each one worth repairing. Use when running the test health maintenance loop, or when asked whether the tests actually check what they claim to. Files issues only; never changes code or tests.

Explain what a Tessl factory on this repository has done and is doing, and why something went wrong. Use when someone asks what their factory, automations, or loops have been doing, what happened on an issue or pull request Tessl worked on, why a run failed or nothing happened after they labeled an issue or left a review, whether anything is stuck or needs them, or how many credits it has used.