An engineering harness for AI coding agents — spec-first, TDD, multi-perspective review, clean commits.
This repository also configures its own agents. See what mx-harness tells them →
Skill Claude Code
Turn a rough idea into an approved design spec: clarifying questions in one batch, 2-3 distinct approaches with trade-offs, spec (and ADR when a real choice was made) written to /.mx/ / /. Hard gate: no implementation until the user approves the spec. Use when starting any feature or non-trivial fix.
Skill Claude Code
Commit all pending changes as one commit per logical concern, following the project's message convention (type prefix, 50-char subject, English). Use when the working tree may hold several changes or the convention must be enforced; a single trivial change can use plain git commit. Usage: /mx-commit [--auto].
Skill Claude Code
Shared execution doctrine for all mx- skills: model dispatch and escalation, delegation templates, judgment rubrics (when done / when to ask / wrong-direction signals), verification contracts, maintenance protocol. Consult when dispatching sub-agents, when repeatedly failing, or before editing any mx-harness file.…
Skill Claude Code
Full development workflow orchestrator: brainstorm → plan → worktree → convergent TDD/review loop → verify → PR. One human gate (spec approval); all other gates auto-proceed. Use when starting a feature or significant change from scratch. Usage: /mx-flow ; /mx-flow status [name]; /mx-flow finish .
Skill Claude Code
Draft a pull request from the feature spec and git log, then publish to GitHub or GitLab (Bitbucket experimental) — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name].
Skill Claude Code
Triage review findings — from local mx-team-review reports or GitHub/GitLab PR comments — into fix / track / skip buckets by validity, severity (P0-P3), and cost, then execute approved decisions. Use after mx-team-review or when handling PR feedback before merge. Usage: /mx-review-triage [--source review | --source pr…
Skill Claude Code
Deep code review of a local git diff or files against this user's own engineering standards (Go, C#), written to a report file that /mx-review-triage consumes. Use before commit/merge when you want the standards-based review, not a quick diff scan. Usage: /mx-team-review [diff-spec] | --repo.
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: