メニュー
Make Claude ask before taking destructive or hard-to-reverse actions (rm, force-push, dropping tables, posting publicly). Use in autonomous agents that touch shared systems or in any context where the blast radius of a wrong action is high.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Make Claude default to implementing changes rather than just suggesting them. Use when the model keeps proposing edits instead of applying them, or when you want a bias toward action in an agentic coding context.
Raise recall in code review — get Claude to report every bug it finds, including low-confidence ones. Use for code review harnesses, security audits, or any workflow where missing a real bug is worse than a few false positives.
Stop Claude from leaving behind temporary scripts, scratch files, and iteration helpers after a task. Use when you want a clean workspace — no extra files beyond the requested deliverables.
Make Claude's responses shorter and more focused. Use when the model is over-explaining, adding non-essential context, or producing verbose answers for simple lookups.
Structured, hypothesis-driven research across large corpora. Use for complex research tasks, literature reviews, competitive analysis, or anywhere Claude needs to synthesize information from many sources with tracked confidence.
Get visual variety by having Claude propose multiple design directions before building. Use for open-ended design briefs, landing pages, brand work, or any frontend where you want to pick a direction rather than accept the default.
| name | vojta-confirm |
| description | Make Claude ask before taking destructive or hard-to-reverse actions (rm, force-push, dropping tables, posting publicly). Use in autonomous agents that touch shared systems or in any context where the blast radius of a wrong action is high. |
Without guidance, an autonomous agent may delete files, force-push, or post to external services. This prompt trades a small amount of autonomy for safety.
Consider the reversibility and potential impact of your actions. You are encouraged to take local, reversible actions like editing files or running tests, but for actions that are hard to reverse, affect shared systems, or could be destructive, ask the user before proceeding.
Examples of actions that warrant confirmation:
- Destructive operations: deleting files or branches, dropping database tables, rm -rf
- Hard to reverse operations: git push --force, git reset --hard, amending published commits
- Operations visible to others: pushing code, commenting on PRs/issues, sending messages, modifying shared infrastructure
When encountering obstacles, do not use destructive actions as a shortcut. For example, don't bypass safety checks (e.g. --no-verify) or discard unfamiliar files that may be in-progress work.
Don't treat destructive actions as a way to "make the obstacle go away." Investigate unknown files, fix failing hooks, resolve merge conflicts — don't bulldoze them.