cmux-ghostty Skill

1---2name: cmux-ghostty3description: "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."4---5 6# cmux Ghostty7 8## GhosttyKit builds9 10Always rebuild the xcframework with Release optimizations:11 12```bash13cd ghostty && zig build -Demit-xcframework=true -Dxcframework-target=universal -Doptimize=ReleaseFast14```15 16## Submodule workflow17 18Ghostty 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.19 20Always 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.21 22```bash23cd ghostty24git remote -v                  # find the manaflow-ai/ghostty remote (usually origin)25git checkout -b <branch>26git add <files>27git commit -m "..."28git push origin <branch>29```30 31To pull in changes from upstream `ghostty-org/ghostty`, add it as an explicit remote first, since no checkout has it by default:32 33```bash34cd ghostty35git remote add upstream https://github.com/ghostty-org/ghostty.git   # once36git fetch upstream37git checkout main38git merge upstream/main39git push origin main40```41 42Then record the new SHA in the parent repo:43 44```bash45cd ..46git add ghostty47git commit -m "Update ghostty submodule"48```49 50## Submodule safety51 52For any submodule (ghostty, `vendor/bonsplit`, `homebrew-cmux`), push the submodule commit to its remote branch **before** committing the updated pointer in the parent repo. Never commit on a detached HEAD or a temporary branch: the parent then points at a SHA unreachable from any remote branch, and a future checkout or CI job fails to fetch it.53 54Verify the commit is reachable from the branch the pointer should track, using the remote you just pushed to:55 56```bash57cd ghostty && git fetch origin main && git merge-base --is-ancestor HEAD origin/main58```59 60## Detailed reference61 62- [references/submodule-safety.md](references/submodule-safety.md): the ordered safe sequence and fork documentation expectations.63