cmux-ghostty

Original：🇺🇸 English

Translated

Ghostty submodule and GhosttyKit workflow rules for cmux. Use when modifying the ghostty submodule, rebuilding GhosttyKit.xcframework, updating the parent submodule pointer, or documenting fork conflict notes.

4installs

Sourcemanaflow-ai/cmux

Added on2026-06-14

NPX Install

npx skill4agent add manaflow-ai/cmux cmux-ghostty

SKILL.md Content

View Translation Comparison →

cmux Ghostty

GhosttyKit builds

When rebuilding GhosttyKit.xcframework, always use Release optimizations:

bash

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

Submodule workflow

Ghostty changes must be committed in the

ghostty

submodule and pushed to the

manaflow-ai/ghostty

fork. Keep

docs/ghostty-fork.md

up to date with any fork changes and conflict notes.

bash

cd ghostty
git remote -v  # origin = upstream, manaflow = fork
git checkout -b <branch>
git add <files>
git commit -m "..."
git push manaflow <branch>

To keep the fork up to date with upstream:

bash

cd ghostty
git fetch origin
git checkout main
git merge origin/main
git push manaflow main

Then update the parent repo with the new submodule SHA:

bash

cd ..
git add ghostty
git commit -m "Update ghostty submodule"

Submodule safety

When modifying a submodule, always push the submodule commit to its remote

main

branch before committing the updated pointer in the parent repo. Never commit on a detached HEAD or temporary branch; the commit can be orphaned and lost.

Verify with:

bash

cd <submodule> && git merge-base --is-ancestor HEAD origin/main

Detailed reference

Read references/submodule-safety.md before committing submodule pointer updates or resolving Ghostty fork conflicts.

cmux-ghostty

NPX Install

Tags

SKILL.md Content

cmux Ghostty

GhosttyKit builds

Submodule workflow

Submodule safety

Detailed reference