CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

tessl/factory-setup

Set up, understand, and change a Tessl factory on a repository: pick automations that fit how you work, such as shipping tickets as pull requests, answering reviews and fixing checks on those pull requests, code review, and scheduled jobs; prepare the repository for agents; write issues for the factory to build; then see what the factory has done, find out why a run failed or never started, and change or extend it.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

linear.mdskills/factory-setup/references/

Linear prerequisites

Check Regional setup first. Linear is US only. For an EU factory, use GitHub issues and perform none of the checks below.

Linear issue to PR needs two things. Check each one and stop with a clear instruction when one is missing.

  1. Linear is connected to the workspace. Run tessl integrations show linear --workspace <workspace> --json. If there is no connection, ask the user to connect Linear at the webUrl in that JSON, or from workspace settings, under Integrations, if it has none. If an entry in integrations has connectionData.reconnectRequired set to true, Linear is connected but has stopped working: say so, and ask the user to reconnect it at the same webUrl. Wait until they say it is done, then run the check again.
  2. A Linear team routes to this project. Linear events reach the project only when a Linear team is mapped to it. Ask the user which team the factory should work on, and ask them to map that team to this project on the Linear integration page, at the same webUrl.

Tell the user how a person starts work: delegate a Linear issue to Tessl and put it in a Todo (unstarted) state. To stop work on one issue, remove the delegate or move the issue to Backlog, Triage, Completed or Canceled. The agent reads the issue again before every comment and push, so this also stops a run in progress from writing more; that run keeps using credits until it notices. Moving the issue to a started state does not stop it, because the agent makes that move itself when it starts.

README.md

tile.json