菜单
FORCE-MODE hotfix: smallest patch → commit → push DIRECTLY to main → follow-up ticket. Needs TERMINAL_FORCE_MAIN=1 (hook-enforced). Use on /emergency-fix or 'this is breaking prod' / 'hotfix' / 'we need to revert now'.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | emergency-fix |
| description | FORCE-MODE hotfix: smallest patch → commit → push DIRECTLY to main → follow-up ticket. Needs TERMINAL_FORCE_MAIN=1 (hook-enforced). Use on /emergency-fix or 'this is breaking prod' / 'hotfix' / 'we need to revert now'. |
/emergency-fix is the one and only skill that intentionally bypasses the
human-merge gate on main/master. It is for production-impacting bugs
that are hurting real users RIGHT NOW. Every other change goes through
/pr-creation → /code-review → human merge.
The skill ONLY works when the caller is launched with
TERMINAL_FORCE_MAIN=1 in the environment. Without it, the global
~/.claude/hooks/block-main-merge.sh PreToolUse hook will refuse the
final git push origin main. Three legitimate ways to be authorized:
emergency-fix / unblock-ci / revert-main agents —
the runner injects the var per-spawn.TERMINAL_FORCE_MAIN=1 claude from
the shell, with a written reason in your scrollback. Do NOT export
the var in ~/.zshrc — that's how accidents happen.If you are NOT in one of those three contexts, this skill is the wrong
tool — use /pr-creation instead.
1. Reproduce the failure (briefly — confirm scope before patching)
│
▼
2. Write the SMALLEST surgical change that stops the bleeding
│ · no refactor · no cleanup · no scope expansion
▼
3. Run the relevant test subset; confirm green
│
▼
4. Commit on main with `fix: <subject>` (Conventional Commits)
│
▼
5. `git push origin main` ← hook bypassed via TERMINAL_FORCE_MAIN=1
│
▼
6. File a backlog ticket capturing real root-cause + proper fix prompt
│ · type: bug · priority: high · source: emergency-fix
▼
7. Hand off with the SHA you pushed + ticket id
/pr-creation)/factory to take/unblock-ci — main CI is red blocking the team; narrow revert/pin/skip./revert-main — narrowly git revert HEAD on main and push.All three flow through the same TERMINAL_FORCE_MAIN=1 carve-out. The
authority is the same; the playbook differs.
Run a scheduled cadence agent from an .agents/<kind>.md spec — isolated worktree, SHA-gated no-op on re-runs, then reports findings or proposes a ticket+MR. Use on /check <kind>, a scheduled-agent run, or wiring a launchd schedule.
Delegate a GitHub/GitLab PR review to Codex: a deterministic preflight does recon, then Codex scores six axes into one artifact at .TerMinal/reviews/<pr>/<sha>.md (v2) or .reviews/<pr>/<sha>.md (legacy v1). Use on /code-review or 'review this PR'.
Continuous autonomous orchestrator — the no-handoff loop around /stacked-mr: reconcile (/merge-sync), build+batch-review a stack to the bar, optionally refill via discovery, repeat. Parks HITL, never merges to main. Use on /factory or 'work the backlog autonomously / continuously'.
Create or update a TerMinal agent from a natural-language request — writes a script-first .agents/<id>.sh + <id>.json sidecar. Use on /new-agent, 'create an agent', or wanting a reusable button/scheduled agent.
Create a global TerMinal persistent memory agent. Use when the user runs /new-persistent-agent or asks for a memory-aware agent that keeps its own INSTRUCTIONS.md, MEMORY.md, STATE.md, JOURNAL.md, and artifacts directory.
Take a backlog ticket from idea to open PR: feature branch → TDD → push → open PR (gh) → link the PR back into the ticket. Does NOT auto-run tests/review. Use on /pr-creation or 'start work on a ticket'.