coder

Implements features and fixes with test-driven development in isolated git worktrees.

Updated May 2, 2026
One-click install
npx skills add https://github.com/whinchman/midi-man-mk3 --skill coder-whinchman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coder
Source: https://github.com/whinchman/midi-man-mk3/tree/main/.claude/skills/coder
Command: npx skills add https://github.com/whinchman/midi-man-mk3 --skill coder-whinchman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating feature implementation across branches, tests, and task tracking is error-prone when done ad hoc. This Skill gives an AI agent a disciplined, repeatable workflow for claiming coding tasks, writing code test-first in an isolated git worktree, and committing changes without ever touching the default branch. ## Core Features & Use Cases - Task-Driven Implementation: Claims pending tasks from markdown task files or a GitHub Projects board, then works through a written plan with small, independently testable steps. - TDD in Git Worktrees: Creates a dedicated worktree branched off the feature branch, writes unit tests first (with all external I/O mocked), runs the full test suite, and commits with conventional or co-authored commit styles. - Safe Handoff: Marks tasks done with a summary of changes and stops — never pushes, merges, or cleans up, leaving review and integration to the Coordinator. - Use Case: A coordinator agent dispatches a task to add a MIDI clock divider to a sequencer engine. The coder agent claims the task, creates a worktree, writes failing unit tests, implements the divider, runs the full suite, commits, and reports back for code review. ## Quick Start Ask the agent to pick up the next pending coder task from the workflow directory and implement it using test-driven development in a new git worktree.

Frequently Asked Questions about coder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a feature with test-driven development in a git worktree?▼

Claim a pending task, write a step-by-step plan, then create a worktree branched off the feature branch with git worktree add. Write unit tests first for each step, implement until they pass, run the full test suite, and commit each step separately.

How does an AI agent claim coding tasks from a workflow board?▼

The agent reads task files in .workflow/tasks/ with Type coder and Status pending, sets the status to in-progress, and follows the acceptance criteria. With the github_project backend, it delegates to a board manager to fetch the next task and update issue status.

Can the coder agent push or merge branches to main?▼

No. The agent never pushes to remote and never merges to the default branch. It marks the task done with a summary of changes and stops, leaving code review, QA, and merging to the Coordinator and Pull Request agents.

What happens when a build script fails due to missing platform SDKs?▼

Cross-platform build failures such as missing xcrun, Xcode, or the Android NDK are not retried. The agent commits the source changes as-is and appends a Manual Steps Required section to the task file describing what the human reviewer must run.

Are integration tests allowed in this TDD workflow?▼

No. Only unit tests are written. Any code path reaching beyond the application boundary, such as HTTP requests, databases, or file system I/O, must be stubbed, mocked, or spied rather than tested against real services.