القائمة
FORCE-MODE: git revert HEAD on main, run the suite, push directly. Needs TERMINAL_FORCE_MAIN=1 (hook-enforced). Use on /revert-main or 'revert main' / 'undo the last commit' / 'roll back HEAD'.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف 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 | revert-main |
| description | FORCE-MODE: git revert HEAD on main, run the suite, push directly. Needs TERMINAL_FORCE_MAIN=1 (hook-enforced). Use on /revert-main or 'revert main' / 'undo the last commit' / 'roll back HEAD'. |
/revert-main is the narrowest FORCE-MODE skill. It does exactly one thing:
git revert --no-edit HEAD on main, runs the suite, pushes. Anything more
than a one-commit revert belongs in /emergency-fix or /unblock-ci.
Same as /emergency-fix: requires TERMINAL_FORCE_MAIN=1 in the env, set by
TerMinal's revert-main agent or a deliberate manual launch. Without it the
global block-main-merge hook refuses the push.
Refuse and surface a human-readable reason if:
1. Confirm you're on the latest main; capture HEAD SHA + subject
│
▼
2. `git revert --no-edit HEAD`
│
▼
3. Run the project test suite; confirm green
│ (if red, abort and file a critical ticket — the revert itself
│ broke something; don't paper over it)
▼
4. `git push origin main` ← hook bypassed via TERMINAL_FORCE_MAIN=1
│
▼
5. File a follow-up ticket
│ title: "Re-do reverted: <original subject>"
│ type: bug · priority: high · source: revert-main
│ body must include: reverted SHA, reason, fix prompt for /factory
▼
6. Hand off with reverted SHA + new main SHA + ticket id
/emergency-fix with a deliberate
multi-commit revert plan, or page humans.)/emergency-fix with a forward-patch.)