cmux-dev-workflow

Orchestrate cmux repo setup, Xcode project normalization, and tagged ExtensionKit development.

25.8k|2.2k|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/manaflow-ai/cmux --skill cmux-dev-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmux-dev-workflow
Source: https://github.com/manaflow-ai/cmux/tree/main/skills/cmux-dev-workflow
Command: npx skills add https://github.com/manaflow-ai/cmux --skill cmux-dev-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Codifies and enforces a repeatable contributor workflow for cmux, covering repo setup, Xcode project normalization, and tagged ExtensionKit development to prevent conflicts during concurrent work.

Core Features & Use Cases

  • Centralizes cmux developer workflow rules for repository setup, Xcode normalization, and tagged sidebar ExtensionKit development.
  • Provides guided setup steps (submodules, tooling, and pre-commit hooks) and clear workflows for creating isolated tagged builds.
  • Uses a structured SKILL.md frontmatter, references files, and supporting scripts to maintain consistency and reduce PR churn.

Quick Start

Run the setup script to initialize submodules and enable the cmux dev workflow.

Frequently Asked Questions about cmux-dev-workflow

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

FAQPage Schema
How do I set up the cmux dev workflow with Xcode and submodules?

To set up the cmux dev workflow, run the provided setup script to initialize Git submodules, normalize Xcode projects, and enable pre-commit hooks for consistent contributor builds.

What is a tagged ExtensionKit build and when do I need it?

A tagged ExtensionKit build isolates sidebar feature development to prevent conflicts during concurrent work. You need it when contributing to cmux to ensure safe collaboration and reduce PR churn.

Why does my Xcode project normalization keep causing conflicts during concurrent cmux development?

Xcode project normalization conflicts occur without isolated tagged builds. Applying the cmux dev workflow enforces structural conventions and prevents overlapping modifications across concurrent contributor branches.

Do I need Git submodules to start contributing to the cmux repository?

Yes, Git submodules are required for initial repository setup. The cmux dev workflow uses a setup script to initialize them alongside required tooling and pre-commit hooks.

What's the best way to normalize an Xcode project for ExtensionKit development?

The best way to normalize Xcode projects for ExtensionKit development is applying the cmux dev workflow rules, which standardize project structure and conventions via structured references and scripts.