Skill Claude CodeCodex
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
Skill Claude CodeCodex
Reviews a technical proposal before implementation. Use for system architectures, feature specs, RFCs, ADRs, and issues that define how a system change should work. Finds material ambiguity and flaws in correctness, scalability, performance, security, operations, and proof.
Skill Claude CodeCodex
Designs and maintains root ARCHITECTURE.md for the intended system, including its data model and shared technical rules. Use for new systems or changes to system boundaries, ownership, storage, or deployment.
Skill Claude CodeCodex
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
Skill Claude CodeCodex
Generates a polished, static HTML reading view from an existing Markdown PRD or technical design. Use when a user asks to render, present, visualize, or make a PRD or design document easier for humans to read in a browser.
Skill Claude CodeCodex
Makes existing code easier to understand without changing behavior. Use to simplify structure, remove duplication or dead code, improve names, or remove unnecessary abstractions.
Skill Claude CodeCodex
Turns a reviewed spec or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.
Skill Claude CodeCodex
Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, and missing proof. Use for code, PR, diff, security, second-opinion, or pre-merge reviews.
Skill Claude CodeCodex
Delivers specs or decided tasks as tested, independently reviewed pull requests. Runs the CI and review repair loop, then leaves passing pull requests open unless merging was explicitly authorized.
Skill Claude CodeCodex
Delivers a spec or decided task through the task-to-pr workflow and merges after all quality and approval gates pass. Explicit invocation grants merge authority for the supplied work.
Skill Claude CodeCodex
Defines system product requirements: users, outcomes, capabilities, business rules, scope, and acceptance. Use for a new service or system, or a change to its product expectations.
Command Claude Code
Create a new branch for a feature, fix, or chore.
Command Claude Code
Clean up local branches and stale references.
Command Claude Code
Stage and commit changes with a well-written message.
Command Claude Code
Explore git history to understand what changed and why.
Command Claude Code
Push the current branch and open a pull request.
Command Claude Code
Squash recent commits into a single clean commit.
Command Claude Code
Command "undo" from owainlewis/youtube-tutorials, covering undo, what happened?, common scenarios, undo last commit, keep the changes and undo last commit, unstage the changes.
Skill Claude CodeCodex
Write a short implementation plan or a longer execution plan before coding. Use when starting new work, when a ticket needs clearer boundaries, when a change spans multiple files or interfaces, or when a multi-hour task needs a living plan.
Command Claude Code
Take a GitHub issue through an isolated implementation and pull request in its own Herdr tab.
Command Claude Code
Read the spec file at $ARGUMENTS.
Command Claude Code
Read the Linear issue $ARGUMENTS using the Linear MCP tool.
Skill Claude CodeCodex
Research video ideas for a topic, preview them, and add only approved non-duplicates to the configured Airtable content pipeline.
Skill Claude CodeCodex
You produce a daily AI news digest. Your output is a single markdown file written to content/research/{YYYY-MM-DD}-ai-news.md and committed to a branch.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: