dotfiles

Delegate a coding task to Codex CLI only when the user explicitly asks to use Codex, delegate to Codex, ask Codex, or have Codex take a pass. Use in Claude Code sessions for user-requested Codex implementation, refactoring, test-writing, CI-fix, or code-exploration work; Claude still writes the brief, scopes the task, reviews the diff, and verifies results.

Run Claude and Codex code reviews in parallel over the current changes, dedupe the findings, then fix the major ones (verifying each first) and summarize. Use when the user wants a thorough, cross-checked review-and-fix from both engines rather than just one.

Run a rigorous one-question-at-a-time grilling session to sharpen a plan, design, architecture, or domain model while maintaining lightweight project docs. Use whenever the user asks to be grilled, stress-test a plan, pressure-test a design, clarify domain terminology, create/update a glossary, or record architecture decisions as ADRs. This skill is standalone; do not rely on separate grilling or domain-modeling skills.

Create, update, monitor, and fix the current branch pull request through repeated review/fix/wait cycles until it is genuinely ready. Use when the user says `/pr`, asks to open/create/update/check/monitor a PR, fix PR checks, address review feedback, keep a PR green, or wait for agent reviewers such as Codex to finish. Do not stop after the first fix if reviewers or CI may still respond; keep iterating until terminal success or a real blocker.

Create static HTML artifacts that are meant to be shared via live-html or public share links. Use this skill whenever building or editing standalone HTML reports, infographics, mockups, visual explanations, dashboards, or any agent-generated HTML likely to be published with share-html or pasted into Slack. Ensures good standalone rendering and Slack/Open Graph unfurls.

Write a clean `handoff.md` for the next session. Use when the user says `handoff`, asks to hand work off to a future Codex session, or wants the current task state summarized into a short next-session brief with files and immediate next action.

Resume work from `handoff.md` without charging ahead. Use when the user says `takeoff`, asks to pick up a previous handoff, or wants Codex to read the saved next-session context, summarize what it is picking up, and wait for confirmation before proceeding.

Commit the current task's changes cleanly. Use when the user asks to commit work on the current branch, says `/gc`, or wants a focused git commit that stages only task-related files with a concise why-oriented message.

Drive work through a test-driven development loop with explicit RED-GREEN-REFACTOR phases. Use when the user asks for TDD, test-first development, red-green-refactor, a failing test first, integration-style boundary tests, or stepwise checkpoints between test writing, implementation, and refactoring.

Reload Pi's extension/runtime from inside an agent turn using delayed wtype input. Use when the human asks for agent-driven development of Pi itself, Pi extension changes, or other Pi configuration work that needs /reload before the agent can test or continue in the updated runtime.

Manage persistent terminal sessions with zmx for long-running or resumable commands, including dev server lifecycle tasks. Use proactively whenever zmx commands will be executed (whether user-requested or agent-initiated), and when users ask to start/stop/restart dev servers, inspect logs/history, monitor status, wait for completion, attach/detach sessions, or run background processes that should survive shell disconnects.