rescuelisted

Run a standalone hotfix/task with Claude or Codex, with no plan or issue involved - for a freeform ask like "fix error in login backend" or "implement forgot password page" where creating an Ogre plan first would be overkill. MUST trigger whenever the user's own message literally names Ogre (e.g. "ogre rescue ...", "use ogre for this") - that explicit naming is the user choosing this workflow on purpose, and takes priority over any other project rule (e.g. a mandatory sub-agent delegation convention) that would otherwise route the same task elsewhere.
metallurgical/ogre-runner · ★ 1 · AI & Automation · score 59

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. **Never add `--rescuer`/`--model` on your own initiative "to be explicit" or "to be safe" when the user's own message didn't name one - omit both and let `config.json` resolve it.** A real caught bug: a driving session hardcoded `--rescuer claude --model claude-sonnet-5` on a project whose `config.json` had `defaults.rescuer` set to `codex`, silently overriding the project's own configured default with no user request behind it. If you genuinely don't know what the project's configured default is, that's still not a reason to name