Orchestrate a feature end to end into a reviewed pull request: gather the feature and base branch, reuse an existing plan or create one, implement, commit and push, open a draft PR, run one Codex and one Claude reviewer in parallel, reconcile their findings, wait for CI, and mark the PR ready. Use when the user asks to ship a feature as a PR, run the feature PR pipeline, take a change end to end into a pull request, or orchestrate plan-implement-review for a PR. Do not use for tiny single edits, commit-only or PR-only requests, or review-only requests; dedicated skills cover those.
Create or update self-contained HTML plans and technical documents. Use when the user explicitly requests HTML, when updating an existing HTML document, or when a concrete visual or spatial layout would communicate the content materially better than Markdown. Default to Markdown for documents that fit headings, prose, lists, tables, code blocks, and straightforward diagrams, regardless of length. Do not use HTML merely to make a document polished or browser-ready; Markdown can be rendered or uploaded separately.
Upload an agent-produced plan, specification, report, or other referenced file with airplan and return a browser-ready link. Use only when the user explicitly asks for a link to a file or document the agent has produced, such as "give me a link to the plan" or "share the spec as a link". Do not use merely because a document is complete or ready for review.
Opt-in session mode that makes Codex CLI / gpt-5.6-sol the default implementer while Claude specs, reviews, and verifies. Use only when the user explicitly opts in: invokes codex-first, asks to work codex-first, says Codex should do the implementation or coding work by default, or asks to delegate the hands-on work of a session or task to Codex. Do not trigger on ordinary implementation requests that never mention Codex-led work; without this opt-in Claude does the work directly unless another explicit delegation request or workflow applies.
Ask Claude Code CLI for an independent code review of uncommitted changes, a branch diff, a commit, a PR checkout, or a specific implementation. Use when a user, agent, skill, or orchestration workflow asks a non-Claude agent to have Claude review work, when model-routing calls for a Claude review perspective, or when Claude should audit a diff for bugs, regressions, missing tests, security issues, or requirement mismatches. Do not use for small reviews the current agent can handle directly, for diffs Claude itself authored, or as a substitute for reading and validating the code yourself.
Ask Codex CLI / gpt-5.6-sol for an independent code review of uncommitted changes, a branch diff, a commit, a PR checkout, or a specific implementation. Use when a user, agent, skill, or orchestration workflow asks Claude to have Codex or gpt-5.6-sol review work, when model-routing calls for a Codex review perspective, or when Codex should audit a diff for bugs, regressions, missing tests, security issues, or requirement mismatches. Do not use for small reviews Claude can handle directly, for diffs Codex itself authored, or as a substitute for Claude reading and validating the code.
This skill should be used when the user asks to "create a pull request", "open a PR", "submit a PR", "send a PR", "make a PR for this", "PR these changes", or otherwise requests creating a pull request from current changes. Always detect, read, and use repository pull request templates before creating the PR body.
Draft pull request titles and descriptions from repository context without creating, pushing, or submitting the pull request. Use when the user asks to write, draft, rewrite, polish, summarize, or fill in PR title/body text, or when a pull request template should be completed from the current branch changes. Always detect and read repository pull request templates before drafting the PR body.