Careful Delete
Before any destructive or irreversible operation (rm -rf, DROP TABLE, DELETE, force push, branch deletion, truncate), orchestrate a safety cycle: assess blast radius → confirm explicitly → document what happened. Chains pre-mortem and you-sure with built-in documentation. No dangerous operation executes without ceremony.
Install
npx skills add ElliotJLT/Claude-Skill-Potions --skill careful-deletegit clone --depth 1 https://github.com/ElliotJLT/Claude-Skill-Potions.git /tmp/Claude-Skill-Potions
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skill-Potions/skills/careful-delete ~/.claude/skills/careful-deletePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Careful Delete <purpose> An elixir for dangerous operations. Destructive commands are irreversible - there's no undo for `rm -rf`, no rollback for a force push to main. This chains risk assessment → explicit confirmation → documentation, adding just enough friction to prevent "oops" moments that ruin your day. </purpose> ## Prerequisites This elixir works best with these skills installed: | Skill | Purpose | If Missing | |-------|---------|------------| | pre-mortem | Blast radius assessment | Falls back to built-in checklist | | you-sure | Explicit confirmation gate | Falls back to built-in confirmation | | retrospective | Document what happened | Skipped (optional) | ## When To Activate <triggers> **File operations:** - `rm -rf` - `rm -r` on directories - Deleting multiple files - Emptying directories **Database operations:** - `DROP TABLE`, `DROP DATABASE` - `DELETE FROM` without WHERE (or with broad WHERE) - `TRUNCATE` - Schema migrations that drop columns/tables **Git operations:** - `git push --force` (especially to main/master) - `git branch -D` (force delete) - `git reset --hard` - `git clean -fd` - Deleting remote branches **Cloud/Infrastructure:** - Deleting cloud resources - Terminating instances - Removing DNS records - Revoking credentials **Keywords in user request:** - "delete all", "remove everything", "wipe", "nuke" - "force push", "hard reset" - "drop the table", "truncate" </triggers> ## Instructions ### Phase 1: Assess Blast Radius
Details
- Skill name
careful-delete- Repository
- ElliotJLT/Claude-Skill-Potions
- Path
skills/careful-delete/SKILL.md- License
- MIT
- Repo updated
- 12 February 2026
FAQ
What does the Careful Delete skill do?
Before any destructive or irreversible operation (rm -rf, DROP TABLE, DELETE, force push, branch deletion, truncate), orchestrate a safety cycle: assess blast radius → confirm explicitly → document what happened. Chains pre-mortem and you-sure with built-in documentation. No dangerous operation executes without ceremony.
How do I install the Careful Delete skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ElliotJLT/Claude-Skill-Potions --skill careful-delete. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Careful Delete popular?
It lives in ElliotJLT/Claude-Skill-Potions, which has 62 GitHub stars and 2 forks.
Related skills
Agent Audit
62ElliotJLT/Claude-Skill-Potions
When reviewing, optimizing, or inheriting an LLM agent, systematically identify what's actually load-bearing vs. cruft. Instruments usage, ablates components, and strips the agent to minimum viable form. Answers: "What can we remove without degrading quality?" The goal is the leanest agent that still works.
Battle Plan
62ElliotJLT/Claude-Skill-Potions
Before ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.
Breadcrumbs
62ElliotJLT/Claude-Skill-Potions
Leaves notes for future Claude sessions in .claude/breadcrumbs.md. At session end or after significant work, records what was tried, what worked, what failed, and context for next time. On session start, reads breadcrumbs to understand history. Session-to-session memory without manual updates.
Code Review Reception
43obra/clank
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
Ijfw Commit
43FerroxLabs/wayland-core
Terse conventional commits. Trigger: commit, git commit, /ijfw-commit
Contribute
43inite-ai/inite-brain-service
Take an idea for INITE Brain from plain words to a green pull request. Use when someone says "I have an idea", "I want to add / change / fix something in Brain", "make Brain do X", or asks how to contribute — engineer or not.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.