/rescue

name: rescue
description: 'Delegate a substantial diagnosis, implementation, or follow-up task to Claude Code through the tracked-job runtime. Args: --background, --wait, --resume, --resume-last, --fresh, --write, --model <model>, --effort <low|medium|high|xhigh|max>, --prompt-file <path>, [task text]. Defaults to opus with no forced effort. Use when Claude should investigate or change things, not when the user only wants review findings.'

Claude Code Rescue

By default, hand this skill off through Codex's built-in `default` subagent. Do not answer the request inline in the main Codex thread. Spawn exactly one rescue forwarding subagent whose only job is to run one companion `task` command and return that stdout unchanged. Foreground rescue responses must be that subagent's output verbatim.

Use this skill when the user wants Claude Code to investigate, implement, or continue substantial work in this repository.

Prefer `$cc:rescue` when the user wants Claude Code to diagnose the issue, validate a risky change by actually editing or testing, apply fixes from a prior review, or carry a task forward across multiple steps. Do not use rescue for "just review this diff" unless the user also wants follow-through work beyond review findings. Do not use rescue merely because the main Codex thread plans to fix things after combining its own review with a separate Claude review. Rescue is only the right delegation when Claude itself is supposed to investigate, edit, test, or otherwise own the follow-through work.

Resolve `<plugin-root>` as two directories above this `SKILL.md` file. Always run the companion from that active plugin root: `node "<plugin-root>/scripts/claude-companion.mjs" task ...`

Raw slash-command arguments: `$ARGUMENTS`

Supported arguments: `--background`, `--wait`, `--resume`, `--resume-last`, `--fresh`, `--write`, `--model <model>`, `--effort <low|medium|high|xhigh|max>`, `--prompt-file <path>`, plus free-text task text

Companion defaults: model=opus, and no effort. The companion forwards `--effort` only when the user passes it, so `fable`, `opus`, `sonnet`, and `haiku` each keep Claude Code's own effort default. Claude Code owns which effort levels each model supports.

Forward `--model` unchanged to the companion. The companion trims surrounding whitespace, canonicalizes the friendly aliases `fable`, `opus`, `sonnet`, and `haiku` to lowercase, then forwards every other `--model` value unchanged to Claude Code. Claude Code owns alias resolution and supported effort levels; `/model` is the authoritative picker for the current account and provider.

Main-thread routing rules:

• If the user explicitly invoked `$cc:rescue` or `Claude Code Rescue`, do not keep the work in the main Codex thread. Delegate it.
• If the user did not supply a task, ask what Claude Code should investigate or fix.
• Treat `--background` and `--wait` as execution controls, not task text.
• `--background` and `--wait` are Codex-side execution controls only. Never forward either flag to `claude-companion.mjs task`.
• The main Codex thread owns that execution-mode choice. It decides whether to wait for the subagent. The child subagent must never reinterpret those flags as companion flags.
• Treat `--model`, `--effort`, `--resume`, `--resume-last`, `--fresh`, and `--prompt-file` as runtime or routing controls, not task text.
• If the user task text itself begins with a slash command such as `/simplify`, `/fix`, or `/review`, treat that slash command as literal Claude Code task text to be forwarded unchanged. Do not execute or reinterpret it in the parent Codex thread.
• `--model` selects the Claude model for the companion `task` command only. It does not select the Codex subagent model.
• If the user explicitly passed `--background`, run the rescue subagent in the background.
• If the user explicitly passed `--wait`, run in the foreground.
• If neither flag is present and the rescue request is small, clearly bounded, or likely to finish quickly, prefer foreground.
• If neither flag is present and the request looks complicated, open-ended, multi-step, or likely to keep Claude Code running for a while, prefer background execution for the subagent.
• This size-and-scope heuristic belongs to the main Codex thread. The child subagent does not get to override it.
• If `--resume` or `--resume-last` is present without `--wait`, and the new instruction is substantial, open-ended, or likely to take more than a quick follow-up, the main thread should usually prefer background execution for the subagent. Keep that as a parent-side choice only. Do not inject `--background` into the child request or the companion command.
• Default to `--write` unless the user explicitly wants read-only behavior or only review, diagnosis, or research without edits.
• If `--resume` or `--resume-last` is present, continue the latest tracked Claude Code task. If `--fresh` is present, start a new task.
• If none of `--resume`, `--resume-last`, or `--fresh` is present, first run:

`node "<plugin-root>/scripts/claude-companion.mjs" task-resume-candidate --json`

• If that helper reports `available: true`, ask the user once whether to continue the current Claude Code thread or start a new one.
• Use exactly these two choices:
• `Continue current Claude Code thread`
• `Start a new Claude Code thread`
• If the user's wording is clearly a follow-up such as "continue", "keep going", "resume", "apply the top fix", or "dig deeper", recommend `Continue current Claude Code thread` first.
• Otherwise recommend `Start a new Claude Code thread` first.
• If the user chooses continue, add `--resume` before spawning the subagent.
• If the user chooses a new thread, add `--fresh` before spawning the subagent.
• If the helper reports `available: false`, do not ask. Delegate normally.
• Do not inspect the repo, do the task yourself, poll job status, or summarize the result in the same turn.
• If a legacy request still includes `--notify-parent-o