machinist
A Claude Code skill for creating, assigning, and monitoring software tasks through Machinist's GitHub issue workflow, intake labels, direct runs, and managed queue.

A Claude Code skill for creating, assigning, and monitoring software tasks through Machinist's GitHub issue workflow, intake labels, direct runs, and managed queue.
Gives coding agents focused skills for turning a rough idea into reviewed work: checking a technical proposal before coding, designing the system architecture, and delivering tested pull requests through review and gated merges.
Code and examples from my YouTube channel tutorials.
You produce a daily AI news digest. Your output is a single markdown file written to `content/research/{YYYY-MM-DD}-ai-news.md`…
Writes root ARCHITECTURE.md from a fixed template: the intended system, a data flow diagram, the data model, and the rules every…
Reviews a technical proposal before any code is written: an architecture, spec, RFC, ADR, or design issue. Finds choices that…
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated…
Generates a polished, static HTML reading view from an existing Markdown PRD or technical design. Use when a user asks to render,…
Makes existing code easier to understand without changing behavior. Use to simplify structure, remove duplication or dead code,…
You take a YouTube video transcript and produce a single LinkedIn post draft.
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub…
Splits a spec into small tasks, each a working slice an agent can finish in one pull request. Use when a spec is too big for one…
Writes the product requirements document (PRD) in root REQUIREMENTS.md as user stories with checkable outcomes. Use for a new…
Research video ideas for a topic, preview them, and add only approved non-duplicates to the configured Airtable content pipeline.
Runs an independent, read-only review of a code change in two parts: does it match the spec, and does it work. Tries bad input,…
Create a new branch for a feature, fix, or chore.
Clean up local branches and stale references.
Stage and commit changes with a well-written message.
Explore git history to understand what changed and why.
Push the current branch and open a pull request.
Review code as a senior engineer would.
Generate a specification for AI-assisted implementation.
Squash recent commits into a single clean commit.
Take a GitHub issue through an isolated implementation and pull request in its own Herdr tab.
Is this you? Claim your profilePut a plugin at the top of Plugins, from $9