Skip to main content
skill CX Codex

gravitas-highstakes — Claude Code skill: checkpoint for destructive changes

gravitas-highstakes — a skill that enforces mandatory confirmation before irreversible operations: database migrations, file deletion, auth changes, production config edits, and force-pushes. Fires when the risk is high.

MIT 446 installs ★ 509 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add udaysharmadev/Gravitas --skill gravitas-highstakes -a claude-code
Open on GitHub

What gravitas-highstakes does

gravitas-highstakes integrates into your workflow and halts execution until you explicitly confirm. Before any destructive operation, the skill states what will change, why it's Tier-2 (irreversible), what risks exist, and requests your go-ahead.

The skill runs a full cycle: plan description → adversarial review → dry-run if available (automatic, no prompt) → stop and ask for confirmation → execute → verify. If anything goes wrong at any stage, it stops and does not proceed further.

Use it for database migrations, file deletion, authentication and access control changes, production environment configs, and git commands that rewrite history. The skill runs on Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.

What it helps with

  • prevent accidental deletion of files or directories
  • review database migrations before they apply
  • avoid mistakes when changing authentication and access rules
  • validate production configs before deployment
  • confirm force-pushes or git history rewrites

Example prompts for the agent

  • Delete all logs older than 30 days from /var/logs
  • Apply a migration that adds a column to the users table
  • Change AUTH_SECRET in production.env

How to install gravitas-highstakes

1Skills CLI (Vercel)

npx skills add udaysharmadev/Gravitas --skill gravitas-highstakes -a claude-code

2Manually: put the files in place

~/.claude/skills/gravitas-highstakes/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/gravitas-highstakes/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about gravitas-highstakes

How do I install gravitas-highstakes in Claude Code?

Run npx skills add udaysharmadev/Gravitas --skill gravitas-highstakes -a claude-code, then locate the file at ~/.claude/skills/gravitas-highstakes/SKILL.md.

What does gravitas-highstakes do?

The skill adds a mandatory checkpoint before irreversible operations — database migrations, file deletion, auth changes, and production config edits. Before executing any such operation, you must explicitly confirm it.

Which operations require confirmation?

The skill triggers on database schema migrations, file deletion, authentication and access control changes, production config changes, and git force-push commands. For each operation, the skill outlines risks and asks for explicit approval.

Source text

SKILL.md · MIT
---
name: gravitas-highstakes
description: >
  Mandatory checkpoint skill for irreversible/high-stakes changes (schema
  migrations, file deletion, auth/security changes, production config,
  force-pushes). Use when a task risks hard-to-reverse damage.
license: MIT
---

# GRAVITAS High-Stakes Skill

For Tier-2 actions (hard-to-reverse, high-stakes), follow this skill
**in addition to** the standard GRAVITAS cognitive loop. This skill
enforces explicit user checkpoints.

---

## Steps

### 1. State the Change and Tier Classification

Before doing anything, explicitly state:
- **What** you plan to change (specific files, tables, configs)
- **Why** this is Tier 2 (what makes it hard to reverse)
- **What** could go wrong

Format:
```
This is a Tier-2 action because: [reason]
Plan:
  1. [specific step]
  2. [specific step]
  ...
Risk: [what could break]
```

### 2. Present the Plan + Adversarial Critique

Run the full Pillar 2 process:
- Write the numbered plan
- Run the adversarial critique (separate reasoning pass)
- Revise the plan based on critique
- Present the revised plan to the user

### 3. Dry Run (if available)

If a dry-run, lint, test, or validation command is available for this
type of change, run it now:

```
# turbo — auto-approved, no user confirmation needed for this step
```

Examples:
- Database migration: `--dry-run` flag
- Config change: schema validation
- Code change: type check + lint
- Deployment: preview environment

### 4. STOP — Wait for Explicit User Confirmation

**Do not execute the plan yet.** Present the plan and ask for confirmation:

```
I've completed the reconnaissance, plan, and adversarial critique.
This is a Tier-2 (irreversible/high-stakes) action.

[Show the plan]

Do you want me to proceed with this plan? Please confirm explicitly.
```

Wait for the user's response. Do not proceed until they confirm.

### 5. Execute the Confirmed Plan

Only after explicit confirmation:
1. Execute each step in the plan
2. After each step, verify it succeeded
3. If any step fails, **stop immediately** — do not continue with the plan

### 6. Re-Verify After Execution

After all steps complete:
1. Run any available post-change verification
2. Re-read the changed files to confirm edits landed
3. If applicable, run the full test suite

Report back with:
- What was changed
- Evidence it's working
- Any concerns or follow-ups

---

## Abort Conditions

Stop the skill and report to the user if:
- A dry-run reveals unexpected side effects
- The plan needs to change mid-execution
- A verification step fails
- The user requests changes to the plan at any point

---

## Example: Database Migration

```
This is a Tier-2 action because: schema changes are irreversible once applied.

Plan:
  1. Create migration file: ALTER TABLE users ADD COLUMN email_verified BOOLEAN DEFAULT false
  2. Run migration against dev database
  3. Update ORM model to include new column
  4. Add NOT NULL constraint after backfill (separate migration)

Risk: If the backfill is incomplete, the NOT NULL constraint will fail.
      If the migration runs in production prematurely, it could lock the table.

Dry run: psql --dry-run (or migration tool's dry-run flag)
```

[Wait for user confirmation]

[Execute and verify]

© udaysharmadev · MIT · udaysharmadev/Gravitas

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set4

Project sponsors

Companies that keep this analytics open