skills.rest
jokerman89
jokerman89COMMUNITY
Explore all skills by this author →
WebsiteGitHub

careful

Wraps high-stakes mutations in per-step confirmation gates with rollback paths and audit logging.

Updated May 27, 2026
Search Tags:#git#rollback#database migration#audit logging#production safety#confirmation gates#mutation control
One-click install
npx skills add https://github.com/jokerman89/lintel --skill careful-jokerman89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: careful
Source: https://github.com/jokerman89/lintel/tree/main/skills/careful
Command: npx skills add https://github.com/jokerman89/lintel --skill careful-jokerman89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? High-stakes operations like production database migrations, destructive git commands, or edits to frozen-zone files carry irreversible risk when executed at normal speed. This Skill adds a slow-down mode that forces explicit confirmation, stated rollback paths, and audit logging before every mutation. ## Core Features & Use Cases - Per-Mutation Confirmation: Every Edit and state-changing Bash command is shown in full and requires operator approval before execution, while read-only commands run freely. - Rollback Planning: Before any mutation, the exact undo command is stated (e.g., git checkout HEAD -- <file>, migration down), so recovery is never improvised. - Audit Logging: Each confirmed mutation is logged to .claude/runtime/audit/careful-mode.jsonl via a unified audit writer, creating a traceable record. - Use Case: Before merging a billing refactor to main with a production deploy following, run /li:careful --for /li:ship so every step of the ship workflow requires confirmation and logs a rollback path. ## Quick Start Ask the agent to enable careful mode with a stated reason before running a production database migration, so each mutation requires confirmation and a named rollback command.

Frequently Asked Questions about careful

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add confirmation prompts before destructive git commands?▼

Enable careful mode with a stated reason, and every state-changing Bash command or file Edit is shown in full and requires explicit operator confirmation before execution. Read-only commands like git status or ls run without prompts.

How do I wrap another workflow in extra safety checks?▼

Use the --for flag, for example /li:careful --for /li:ship, to run another skill's workflow under careful mode. Every step then requires confirmation, and shipping to main demands triple confirmation.

When should I not use careful mode?▼

Avoid it for routine code edits, read-only investigation, and time-critical incident response. The per-step confirmation overhead slows routine work, and live incidents need urgency-with-rigor rather than per-mutation gates.

What happens if a mutation succeeds but verification fails?▼

The skill states the divergence and names the rollback command but does not auto-rollback. The operator decides the next move, keeping humans in control of recovery for high-stakes changes.

Does careful mode keep an audit trail of changes?▼

Yes, each confirmed mutation is logged as one line to .claude/runtime/audit/careful-mode.jsonl via a unified audit writer. If the audit log is unwriteable, the skill treats it as blocking and asks before proceeding.

Related Skills

Explore More Software Engineering Skills→
tranhieutttranhieutt
70

freeze

Lock a codebase by writing a .freeze file with reason, timestamp, and branch.

Community
Intermediate
Elijah-JElijah-J

ar-closeout

Summarize perf autoresearch results, verify final state, and archive artifacts for handoff.

Community
Advanced
garethrhughesgarethrhughes
5

infosec

Audit staged changes for security, privacy, and compliance violations before merge.

Community
Advanced
logo-solutionslogo-solutions

ci-cd-and-automation

Automate CI/CD pipeline setup and enforcement for GitHub Actions workflows.

Official
Advanced