fabro

Generate and update the product changelog in Mintlify docs. Use when the user asks to update the changelog, add a changelog entry, document recent changes, or write release notes. Reads git history on main, filters to user-facing changes, and writes dated MDX files to docs/public/changelog/.

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, keeping pull requests moving, 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.

Implement a GitHub issue that a person labelled `tessl`: read the issue and the repository, make the change on the issue's own branch, run the tests, and open one pull request for the issue. Stops without a trace when a person has taken the issue back.

Implement a Linear issue that a person delegated to Tessl: read the issue and the repository, make the change on the issue's own branch, run the tests, and open one pull request for the issue. Stops without a trace when a person has taken the issue back.

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.

Apply this Rust style guide when writing, reviewing, refactoring, or configuring Rust code for this project. Covers Rust 2024/MSRV, library vs application conventions, public API design, errors, panics, ownership and cloning, async/Tokio/concurrency, tracing, rustfmt/Clippy, testing with nextest, and unsafe/macro policy. Also use when setting up new Rust projects, investigating Rust performance, verifying library releases, or reviewing Rust code changes.

Get a pull request that Tessl opened for a Linear or GitHub issue ready for its owner: answer review feedback, fix failing checks and conflicts on the existing branch, and tell the owner when it is ready. Opens no new pull request.

Update documentation in docs/public/ based on recent code changes. Reads git history since a watermark commit, maps changed files to doc pages, and makes surgical edits to keep docs in sync with code.