revert-main

Stars7

Forks2

UpdatedJuly 18, 2026 at 14:58

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'.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

trevormil

trevormil/TerMinal

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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 — undo the most recent main commit

/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.

[1] Authority

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.

[2] Refusal cases

Refuse and surface a human-readable reason if:

HEAD is already a revert commit (would be a no-op or destructive).
HEAD is more than 24h old — the team has likely built on top of it and a straight revert may break work-in-flight. Page humans instead.
The most recent commit is on a non-default branch.
The working tree is dirty.

[3] Sequence

   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
        │  assign exactly one owner agent via list_agents
        │  body must include: reverted SHA, reason, fix prompt for /factory
        ▼
   6. Hand off with reverted SHA + new main SHA + ticket id

[4] When NOT to use

More than one commit needs reverting. (→ /emergency-fix with a deliberate multi-commit revert plan, or page humans.)
The bad commit is several commits back and reverting it would conflict. (→ /emergency-fix with a forward-patch.)
The revert touches data migrations or schema changes. NEVER auto-revert those — surface a critical ticket and stop.

More from this repository

same repository

code-review

trevormil/TerMinal

Compatibility launcher for the code-review agent. Delegates a GitHub/GitLab PR review to Codex: 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'.

2026-07-187

digest

trevormil/TerMinal

Human-review digest for a PR/MR — chunks the diff into a noise-filtered, risk-ranked, code-first review surface (green/red diffs, 🟢/🟡/🔴, design-decision callouts) WITHOUT abstracting the code away. Deterministic chunker + one bounded codex pass. Sits alongside /code-review (the gate) and /iterate (tests). Use on /digest or 'digest this PR for review'. Renders in TerMinal.

2026-07-187

document-audit

trevormil/TerMinal

Audit docs/ and ~/.claude/docs/ for rot — broken refs, stale runbooks, ADR contradictions, architecture drift, orphan CLAUDE.md. Reports only; never auto-edits. Use on /document-audit or 'check doc health'.

2026-07-187

document

trevormil/TerMinal

Sweep recent changes and propose doc updates (ADRs, runbooks, learnings, architecture, per-folder CLAUDE.md), one candidate at a time. Use on /document, 'capture decisions', or natural post-commit/post-PR pauses.

2026-07-187

emergency-fix

trevormil/TerMinal

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'.

2026-07-187

enqueue-request

trevormil/TerMinal

Enqueue a one-off TerMinal automation-inbox request (can create Activity, tickets, HITL, agent runs, or background tasks). Use on /enqueue-request or to queue a durable local automation request.

2026-07-187

/revert-main — undo the most recent main commit

[1] Authority

[2] Refusal cases

Refuse and surface a human-readable reason if:

HEAD is already a revert commit (would be a no-op or destructive).

HEAD is more than 24h old — the team has likely built on top of it and a straight revert may break work-in-flight. Page humans instead.

The most recent commit is on a non-default branch.

The working tree is dirty.

[3] Sequence

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 │ assign exactly one owner agent via list_agents │ body must include: reverted SHA, reason, fix prompt for /factory ▼ 6. Hand off with reverted SHA + new main SHA + ticket id

[4] When NOT to use

More than one commit needs reverting. (→ /emergency-fix with a deliberate multi-commit revert plan, or page humans.)

The bad commit is several commits back and reverting it would conflict. (→ /emergency-fix with a forward-patch.)

The revert touches data migrations or schema changes. NEVER auto-revert those — surface a critical ticket and stop.