Linear Orchestrator

Linear Orchestrator

**Tickets in. Reviewed pull requests out. Nobody watching.**

A [Claude Code](https://claude.com/claude-code) skill that runs your Linear board overnight and hands you a morning of pull requests to read.

There is an experimental second generation, [linear-orchestrator2](https://github.com/janwilmake/linear-orchestrator2), which moves the whole conversation — body, screenshots, review, steering — into the Linear ticket. This repo is the maintained generation: the conversation lives on the pull request, and you steer by commenting there.



What makes it different

**The whole interface is two surfaces.** A ticket in Linear, and a comment on a pull request. There is no chat window to steer, no label to remember, no plan to approve inside the tracker. To change the direction of the work you comment on the PR, and the loop reads it, answers it by name, and acts on it. That works on a **merged** PR too, which is where it earns its keep: merge, note the follow-up work the PR spotted but left out of scope, and the loop turns your note into the next ticket by itself. Teammates can steer it the same way, on purpose.

**Draft means something.** A PR leaves draft only on evidence — a review, a fix pass over that review, a screenshot when a user can see the change, no merge conflict, and CI green on the head commit. It never leaves draft on an agent's say-so. So what is not a draft in the morning is what is actually ready, and the drafts are the pile you can ignore until you have time.

**Idle costs nothing.** N