Create a self-contained, copy-ready handoff prompt from the current conversation, preserving decisions, rationale, unresolved questions, next steps, work status, and authority boundaries. Do not send messages or manage Codex tasks.
Statically review one user-specified GitHub pull request and publish one review. Do not use for general review drafting, local code review, or multi-PR work.
Resolve Git merge, rebase, cherry-pick, or PR branch conflicts against a fetched remote base branch. Use when a user asks to fix conflicts, update a branch onto its remote base, make a branch mergeable, resolve GitHub PR conflicts, continue an interrupted conflict operation, or prepare a conflicted branch for merge…
Destructive Git cleanup workflow that keeps only the main worktree and local main branch, then updates main; not for routine status checks, partial cleanup, or implicit repository hygiene.
From a host-identified ephemeral Codex side conversation, preview and send a structured handoff to the uniquely verified main task, then open it. Fail closed outside that side-conversation boundary, for subagent coordination, or when the target is ambiguous.
Preflight a tracker issue, linked change, or branch-scoped work reference before implementation; stop with a tracker draft and do not implement or mutate trackers.
Close a Linear issue only after independent evidence review; move it to the team's completed state and leave one closeout comment with retry-safe reuse. Stop without mutation on incomplete work, reviewer veto, uncertainty, stale evidence, unsafe overwrites, or unavailable subagents.
Translate and handle PR/code review feedback in the user's resolved locale, including requested changes, decision interviews, confirmed fixes, verification, reviewer follow-up, per-thread replies and resolves, optional PR body updates, and re-review requests.
Recommend what to do next for current work by inspecting available work signals. Do not use for handoff files, implementation planning, status reports, or broad backlog triage.
Draft and optionally file a GitHub issue for a Grimoire documentation, skill, plugin packaging, Codex harness, or workflow change. Use when a user wants to report a reusable Grimoire problem or improvement upstream.
Use at the start of every task in an environment where Grimoire skills are available. Requires checking and loading applicable Grimoire skills before answering, asking clarifying questions, planning, inspecting files, using tools, or editing.