rescuelisted
Install: claude install-skill metallurgical/ogre-runner
# /ogre:rescue
Use this skill when the user wants something done right now - a quick fix, a small
standalone feature, a one-off task - and does NOT want to go through `/ogre:feature`
(issue -> plan -> review -> execute) first. There is no plan, no job, no issue file.
If the user is already mid-plan on an existing Ogre issue and wants to add scope to
it, that's `/ogre:add-blocker`, not this.
## Inputs
Accept the task description either as a plain positional argument or via `--statement`:
- `/ogre:rescue "fix error in login backend"`
- `/ogre:rescue --statement "implement forgot password page"`
Optional flags (same shape as `/ogre:execute`'s):
- `--rescuer claude|codex` - who does the work. Omitted: falls back to
`defaults.rescuer` in `.ai/.ogre/config.json`, then `claude`. `rescuer` is its
own config role, separate from `defaults.executor` - a project can pin a
different CLI/model for one-off rescues than for plan execution.
- `--model MODEL`
- `--reasoning LEVEL` - reasoning effort for the rescuer (`claude -p` gets
`--effort LEVEL`, `codex exec` gets `-c model_reasoning_effort=LEVEL`). Omit it to
use the CLI's own default; Ogre never forces one.
- `--name slug` - override the auto-derived slug used for this rescue's log/tmp
paths (`.ai/.ogre/{tmp,logs}/issue-rescue-<slug>/`). Without it, Ogre derives one
from the first few words of the task text plus a short uuid suffix, same scheme
as `/ogre:feature --statement`'s auto-name.
- `--main` - run inline in t