Changelog
All notable changes to mx-workflow are documented on this page. The format follows Keep a Changelog, and the project uses Semantic Versioning.
Unreleased
Section titled “Unreleased”- Smart pipeline routing for
/mx:loop— auto-classifies tickets into Bug Fix, Feature, Simple/Docs, or Refactor pipelines with tailored sub-agent workflows (EIT-58) --branch-per-ticketmode for/mx:loop— creates isolated branches with auto-PR creation per ticket (EIT-59)- Per-ticket pipeline override syntax (e.g.,
EIT-42:A) for/mx:loop
Changed
Section titled “Changed”/mx:looppre-flight summary now shows pipeline classification per ticket/mx:loopfinal report includes pipeline breakdown stats, branch names, and PR URLs/mx:helpupdated with new/mx:loopflags and pipeline routing
1.1.1 — 2026-03-01
Section titled “1.1.1 — 2026-03-01”Changed
Section titled “Changed”- Add
/mx:prefix to all commands in/mx:helpreference card for consistency
1.1.0 — 2026-03-01
Section titled “1.1.0 — 2026-03-01”This release adds seven new commands, a new agent, and significant documentation improvements.
/mx:loopcommand — sequential ticket processor that fetches Linear tickets and processes them one-by-one via sub-agents/mx:prcommand — create PRs with auto-generated summaries and agent review findings (EIT-28)/mx:branchcommand — ticket-encoded branch creation usingMX_BRANCH_PATTERN(EIT-29)/mx:agentscommand — discover available agents with purposes and command references (EIT-30)/mx:depscommand — dependency security audit, outdated version checks, and unused package detection (EIT-31)/mx:versioncommand — centralized version management across plugin.json, marketplace.json, and CHANGELOG.md (EIT-36)mx-performance-auditoragent — performance analysis covering algorithmic complexity, memory, I/O, frontend, and database patterns (EIT-32)--dry-runflag for/mx:shipit— preview what would be committed and pushed without actually doing it (EIT-33)mx-comment-analyzerintegrated into/mx:implementreview pass for comment quality checks (EIT-41)- Getting Started walkthrough in README (EIT-37)
- Troubleshooting section in README (EIT-38)
- Example project configurations in scope-mappings for frontend SPA, backend API, monorepo, and CLI tool (EIT-39)
- PRD vs Plan usage clarification in README (EIT-40)
- Database rollback/cleanup guidance in
/mx:e2e(EIT-42) - CHANGELOG.md following Keep a Changelog format (EIT-49)
- Audited and fixed
allowed-toolsdeclarations across 5 commands — added missing tools, removed unused ones (EIT-35)
Changed
Section titled “Changed”- Version management documented in CLAUDE.md now references
/mx:versioncommand /mx:helpupdated with all new commands across implementation, discovery, release, and anytime sections
1.0.1 — 2026-02-28
Section titled “1.0.1 — 2026-02-28”- Replace non-standard “ultrathink” language with clear instructions in check-ignores command (EIT-26)
- Standardize
.agents/output directory naming to all-lowercase-hyphenated format (EIT-34)
Changed
Section titled “Changed”- Document output directory convention in CLAUDE.md
1.0.0 — 2026-02-27
Section titled “1.0.0 — 2026-02-27”The initial release of mx-workflow, covering the full development lifecycle from planning to shipping.
- 15 slash commands for the full dev lifecycle: ticket intake, planning, implementation, quality checks, conventional commits, MR creation, batch AI implementation, and multi-agent team builds
- 6 specialized agents for code review, testing, debugging, and analysis
- Plugin manifest (
plugin.json) and marketplace configuration - CLAUDE.md with project development guidelines
- Scope mappings and agent browser references