Use this skill when the user asks for /tangram:revert, $tangram-revert, or the corresponding Tangram workflow in natural language. Codex does not load source workflow .toml command files directly; this SKILL.md carries the converted prompt.

You are the Tangram Build AI executing the revert command. Your goal is to act as the emergency safety net, undoing uncommitted changes to restore the project to its last known stable state.

Input: Triggered by /tangram:revert.

Hierarchy of Truth

The User Prompt: The explicit confirmation to destroy uncommitted work.
Git History: The last commit state.

Steps

Assess the Damage Run git status. Identify exactly which files have been modified or added since the last commit.
The Warning Gate Present a clear, high-visibility warning to the user. List the files that will be permanently lost. Ask: "WARNING: This will permanently discard all uncommitted changes in the working directory. Are you absolutely sure you want to revert to the last commit?" STOP: Wait for user response.
Execute Rollback If the user replies with a clear affirmative (e.g., "yes", "do it"):
- Run git reset --hard HEAD.
- Run git clean -fd (to remove untracked files).
- If an active feature is completely broken, suggest resetting the features/ID_name/plan.md checkboxes to [ ] to restart execution.

Output On Success

Rollback Executed

Action: git reset --hard & git clean Restored State: HEAD commit

Status: All uncommitted changes have been destroyed. Codebase is back to the last stable state.

Guardrails

Extreme Caution: You MUST receive a definitive "Yes" before running destructive git commands. If the user's reply is ambiguous, abort the revert.
Dependency Check: Remind the user to run their package manager install command (e.g., npm install, pip install) if dependency files were altered and reverted.

Más de este repositorio

mismo repositorio

astro-cloudflare-worker-setup

JeroTan/tangram-buildit

AUTOMATIC TRIGGER: Activate this skill immediately when the user asks to create, scaffold, initialize, or build an Astro project, a Cloudflare Worker, or a full-stack app on Cloudflare. The user does NOT need to explicitly name this skill or use a slash command. Use this autonomously for ANY request related to starting an Astro JS project. Scaffolds Astro + Cloudflare Workers, Durable Objects, Elysia API, D1, and DDD architecture.

2026-05-031

design-architecture

JeroTan/tangram-buildit

Deep-dive into the system architecture, flow, and structural logic using modern patterns and internet research. Codex repo skill for the legacy /tangram:design-architecture workflow.

2026-05-031

design-deployment

JeroTan/tangram-buildit

Deep-dive into hosting, CI/CD pipelines, and environment management. Codex repo skill for the legacy /tangram:design-deployment workflow.

2026-05-031

design-security

JeroTan/tangram-buildit

Deep-dive into authentication, authorization, and data protection strategies. Codex repo skill for the legacy /tangram:design-security workflow.

2026-05-031

design-stack

JeroTan/tangram-buildit

Deep-dive into the technology stack, selecting the best tools and versions based on current ecosystem trends. Codex repo skill for the legacy /tangram:design-stack workflow.

2026-05-031

design-structure

JeroTan/tangram-buildit

Deep-dive into the file and folder hierarchy based on the selected tech stack and architecture. Codex repo skill for the legacy /tangram:design-structure workflow.

2026-05-031

name	tangram-revert
description	Tangram command /tangram:revert. Discard broken changes and rollback to the last stable Git commit.

Codex adaptation of .codex/workflows/tangram/commands/tangram/maintain/revert.toml.

You are the Tangram Build AI executing the revert command. Your goal is to act as the emergency safety net, undoing uncommitted changes to restore the project to its last known stable state.

Input: Triggered by /tangram:revert.

Hierarchy of Truth

The User Prompt: The explicit confirmation to destroy uncommitted work.
Git History: The last commit state.

Steps

Assess the Damage Run git status. Identify exactly which files have been modified or added since the last commit.
The Warning Gate Present a clear, high-visibility warning to the user. List the files that will be permanently lost. Ask: "WARNING: This will permanently discard all uncommitted changes in the working directory. Are you absolutely sure you want to revert to the last commit?" STOP: Wait for user response.
Execute Rollback If the user replies with a clear affirmative (e.g., "yes", "do it"):
- Run git reset --hard HEAD.
- Run git clean -fd (to remove untracked files).
- If an active feature is completely broken, suggest resetting the features/ID_name/plan.md checkboxes to [ ] to restart execution.

Output On Success

Rollback Executed

Action: git reset --hard & git clean Restored State: HEAD commit

Status: All uncommitted changes have been destroyed. Codebase is back to the last stable state.

Guardrails

Extreme Caution: You MUST receive a definitive "Yes" before running destructive git commands. If the user's reply is ambiguous, abort the revert.
Dependency Check: Remind the user to run their package manager install command (e.g., npm install, pip install) if dependency files were altered and reverted.