Menú
FORCE-MODE: main CI is red — apply the narrowest of revert bad SHA / pin dep / skip documented-flaky test, pushed directly to main. Needs TERMINAL_FORCE_MAIN=1. Use on /unblock-ci or 'main CI is broken' / 'green main'.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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'.
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'.
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.
| name | unblock-ci |
| description | FORCE-MODE: main CI is red — apply the narrowest of revert bad SHA / pin dep / skip documented-flaky test, pushed directly to main. Needs TERMINAL_FORCE_MAIN=1. Use on /unblock-ci or 'main CI is broken' / 'green main'. |
/unblock-ci is a FORCE-MODE skill (see /emergency-fix for the full authority
explanation). It bypasses the human-merge gate ONLY for the narrowest possible
fix that returns the default-branch CI to green.
Same as /emergency-fix: requires TERMINAL_FORCE_MAIN=1 in the env, set by
TerMinal's unblock-ci agent or a deliberate manual launch. Without it the
global block-main-merge hook refuses the push.
Pull the failing run's logs (gh run view --log / glab ci view) and
classify the failure:
| Class | Symptom | Narrowest fix |
|---|---|---|
| (a) Regression from the last merge | new failure on first run after a known commit | git revert <bad-sha> |
| (b) Flapping test | same test fails intermittently across reruns | mark with project skip/retry convention |
| (c) Dep / install break | npm install / bun install / pip install fails | pin the last-working version |
| (d) Infra | runner died, registry down, network out | NO fix — file a ticket and exit |
If the failure is genuinely outside the fix budget of those four classes, file a ticket and stop. Do not paper over a real bug.
1. Pull failing CI logs; classify (a/b/c/d above)
│
▼
2. Apply the narrowest fix matching the class
│ (a) git revert <bad-sha>
│ (b) mark test skip/retry per project convention
│ (c) pin the dep
│ (d) exit — file ticket only
▼
3. Run the project's test suite locally; confirm green
│
▼
4. Commit on main; push directly (`git push origin main`)
│
▼
5. File a follow-up ticket
│ type: testing | ci | dependency · priority: high
▼
6. Hand off with the action taken + new main SHA + ticket id