Cmux Ghostty

This handles the Ghostty terminal submodule workflow for the cmux project, including rebuilding the GhosttyKit.xcframework with proper Release optimizations, managing the fork relationship with upstream, and updating submodule pointers safely. You'd use this when modifying Ghostty itself, syncing with upstream changes, or documenting fork conflicts. The skill emphasizes submodule safety rules like never committing on detached HEAD and always pushing submodule commits before updating the parent pointer. It's focused on a specific project setup, so only useful if you're working on cmux or have a similar forked submodule workflow where you need to maintain changes against an upstream while building platform specific frameworks.

skills.sh installs: 4.9K
GitHub stars: 28.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add manaflow-ai/cmux --skill cmux-ghostty --agent claude-code

Installs into .claude/skills of the current project.

Files

cmux Ghostty

GhosttyKit builds

Always rebuild the xcframework with Release optimizations:

cd ghostty && zig build -Demit-xcframework=true -Dxcframework-target=universal -Doptimize=ReleaseFast

Submodule workflow

Ghostty changes are committed in the ghostty submodule and pushed to the manaflow-ai/ghostty fork. Keep docs/ghostty-fork.md current with fork changes and conflict notes.

Always run git remote -v first and push to whichever remote is manaflow-ai/ghostty. .gitmodules sets the submodule URL to that fork, so in a normal checkout it is origin; older setups tracked upstream as origin and added the fork as manaflow. Substitute the right name below.

cd ghostty
git remote -v                  # find the manaflow-ai/ghostty remote (usually origin)
git checkout -b <branch>
git add <files>
git commit -m "..."
git push origin <branch>

To pull in changes from upstream ghostty-org/ghostty, add it as an explicit remote first, since no checkout has it by default:

SKILL.md on GitHub