dotfiles

Run jj commit. Use when current work is ready to commit and Codex should inspect the changes, use any provided context, and create a reasonable detailed Jujutsu commit message.

Commit changes, push to remote, and create a PR skill

Create a set of phases for a large project

Read a PR review guide and review the code. Use when `review-guide.md` already exists and Codex should follow that guide, inspect the referenced changes, and append findings without overwriting prior notes.

Fix merge conflicts. Use when the current repository has unresolved conflicts and Codex should inspect both sides, trace the surrounding history, resolve the files carefully, and ask for help only when the correct resolution is unclear.

Address AI review comments in source files. Use when repository files contain AI review markers and Codex should locate them, implement the requested fixes, remove the markers, and validate the changes.

Read current_progress.md and continue from there. Use when a project has a `current_progress.md` checkpoint and Codex should restore the saved context, resume the next steps, and keep the file updated while working.

Converts "AI" comments in local files into Github PR review comments

Investigates and fixes failing GitHub pull request checks by querying the GitHub API through the gh CLI, inspecting workflow runs and logs, making code changes, and verifying the likely fix locally. Use when the user asks to fix failing CI on a PR, investigate red GitHub checks, repair a broken pull request build, or review a PR with optional guidance about how the fixes should be approached.

Address an issue on GitHub. Use when given a GitHub issue number and Codex should read the issue body and comments, then create a plan for addressing the work described there.

Create a new Jujutsu bookmark and push it to GitHub. Use when current work is ready to publish on a fresh branch and Codex should commit pending changes if needed, choose a good bookmark name, create it, track it, and push it.

Rebase and repair stacked branches in a Jujutsu (jj) repository after the current base branch has been updated. Use when the user says they are on an updated base branch and need to update, rebase, evolve, resolve conflicts in, validate, or adapt all child/stacked jj branches on top of it.

Generate a PR review guide. Use when a branch needs a detailed walkthrough for review and Codex should group the changed files, write `review-guide.md` and `review-guide.json`, then perform the review and add findings to the guide.

Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".

Save current progress, plan, and thinking to `current_progress.md`. Use when Codex should write a resumable checkpoint for the current task, status, decisions, todo list, and next steps.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

Address pull request review comments