machinist

# Machinist Machinist turns one open GitHub issue into a planned, implemented, independently reviewed, and checked pull request. It never merges the pull request. ## Core model - A task is one open GitHub issue in the target repository. - Assigning a task means starting `machinist run` or queuing `machinist submit`. - Foreman lifecycle labels report workflow state. Configured GitHub intake labels can enqueue managed work. - Reassign the same issue to resume existing work. The foreman recovers its branch, worktree, pull request, checks, and repair count. - When `MACHINIST_RUN_ID` is set, the agent is already inside a Machinist run. Follow the assigned role and do not start or submit another run. ## Create a task Reuse a supplied issue when it is open and belongs to the current repository. Otherwise create one issue with `gh issue create`. Keep it focused on one observable outcome and preserve the user's constraints. Do not invent implementation details that the request does not decide. ```sh gh issue create --title "<short outcome>" --body "<problem, outcome, constraints, and acceptance evidence>" ``` Use the issue URL returned by GitHub for every later command. ## Assign a task Use direct mode for immediate local work. Pass an absolute Git worktree path: ```sh machinist run \ --command=foreman \ --repo=/absolute/path/to/repository \ --prompt="Complete https://github.com/owner/repository/issues/123" ``` Use managed mode when the control plane and worker ...