Jimothy
Download
Use case · Issues → pull requests

Label an issue.
Review the pull request.

Label an issue in Linear, Jira or GitHub. Claude Code plans and builds it on its own branch, your tests run, Codex reviews the diff, and you get a pull request to approve. The issue is updated at every step.

Set it upDownload Jimothy
LinearENG-142Add CSV export to the reports pagejimothy
Pipeline
  1. Plan Claude Code · opus
  2. Implement Claude Code · sonnet
  3. Run tests npm test
  4. Review Codex · ↻ 1
  5. Human approval you
Pull requestacme/app#318ENG-142: Add CSV export to the reports pageIn Review
Why it holds up

What the pipeline does for you

  • Work goes back until it passes

    Failing tests or a CHANGES_REQUESTED review send the work back to the implementer with the feedback attached, up to twice each.

  • Its own branch and worktree

    Each run gets a fresh git worktree on a branch like jimothy/eng-142, so several issues can be in flight without colliding.

  • You are the gate

    Nothing is pushed until you approve, from the app, the tray or your phone. Reject with a comment and the implementer runs again with it.

  • The tracker stays current

    Jimothy moves the issue to In Progress, then In Review, and comments the run summary and PR link. Jira-style PR titles show up in Jira’s development panel.

Set it up

Four steps, once

  1. Sign in to Linear, Jira or GitHub under Accounts.
  2. Pipelines → New pipeline → Feature: Plan → Build → Review → PR, and point it at your git clone.
  3. Add a trigger for the jimothy label (or a hand-off status).
  4. Label an issue.
More use cases

Same engine, different jobs

For engineering

Schedule → Pull request

Nightly maintenance

A schedule updates dependencies overnight, fixes what breaks, and opens a PR only if something changed.

See how it runs →GitHub → Comment

Specs from vague issues

A fuzzy issue gets a spec with acceptance criteria and open questions, posted back after you approve it.

See how it runs →

Beyond engineering

Webhook → Reply

Support reply drafts

New tickets are triaged and answered in your voice, within your policies. You approve before anything is sent.

See how it runs →Schedule → Slack

Weekly product updates

Every Friday the week’s changes become a customer-facing “What’s new” post, ready to approve and publish.

See how it runs →Webhook → CRM

Inbound lead research

Each contact-form lead gets a cited research brief, a fit rating and a first reply before you’ve opened the email.

See how it runs →
Any trigger → anything

Build your own

Agent, shell and approval steps in a DAG, started by an issue, a schedule or a webhook. Or describe it and let Jimothy draft the pipeline.

Pipeline docs →