Menu
Bring the user's local Helix fork up to date: fetch, rebase merge commit, resolve conflicts, rebuild.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Debugging a ghostty crash
Drive a real browser during frontend work — verify a change rendered, click through a flow, fill forms, read console errors, take screenshots, or debug performance/memory/network. Use whenever interacting with a local web app in a browser (Playwright script templates, chrome-devtools tradeoffs, SPA mock-API gotchas).
How to use the tviz CLI to read and write Things 3 tasks
For non-Codex agents, get a Codex second opinion on your changes. Claude sends the diff to Codex for review, discusses the feedback, and synthesizes actionable results.
Productivity coach
Read Oxide RFD contents, metadata, and images by number using rfd-cli. Use when an RFD comes up (e.g. "RFD 63", "what does the networking RFD say") and you need the actual text.
| name | helix-update |
| description | Bring the user's local Helix fork up to date: fetch, rebase merge commit, resolve conflicts, rebuild. |
The user runs a custom Helix build that merges two upstream forks on top of helix-editor/master:
search_position (useche/helix) — adds match counter limitsteel-event-system (mattwparas/helix) — Steel scriptingTheir merge commit (description: "merge in search position PR") sits on top with both as parents. Updating means rebasing it onto the new tips of both branches.
cd /Users/david/repos/helixjj git fetch --all-remotesjj log -r 'heads(::search_position+ & ::steel-event-system+)' --no-graph -T 'change_id.short() ++ " | " ++ description.first_line() ++ "\n"'
jj log output — it's the merge with two branch parents.)jj rebase -s <change-id> -d search_position -d steel-event-systemjj resolve --tool mergiraf. Inspect with jd (alias for jj diff) and confirm before squashing.jj squash (run from the conflict-resolution rev created by jj resolve).killall hx; cargo install --profile opt --config 'build.rustflags=["-C", "target-cpu=native"]' --path helix-term --locked && cargo clean
cargo xtask steelThe build takes a while — run it in the background and report when done. If mergiraf can't resolve everything, stop and show the user the conflicted files rather than guessing.