nuke

Rebuild broken services by tearing down faulty implementations and scaffolding fresh replacements.

3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/marcmunoz-uno/jailbreak --skill nuke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuke
Source: https://github.com/marcmunoz-uno/jailbreak/tree/main/skills/nuke
Command: npx skills add https://github.com/marcmunoz-uno/jailbreak --skill nuke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of services becoming too entangled or corrupted to fix reliably, by performing a controlled teardown and fresh rebuild while preserving critical data and interfaces.

Core Features & Use Cases

  • Preserve data and configuration: Backs up databases, configs, and state before any teardown, and keeps rollback-ready old versions until the new build is validated.
  • Preserve interfaces and integrations: Maintains the same API contracts, URLs, webhooks, and MCP tool interfaces so downstream clients keep working.
  • Parallel rebuild with verification gates: Uses parallel agent waves to rebuild components, then runs acceptance tests and integration checks before cutover.

Use case example: A production service repeatedly fails due to escalating tech debt and config corruption; use nuke to back up state, rebuild the service architecture, migrate the existing data, redeploy, and verify everything before switching traffic.

Quick Start

Ask the AI to run the nuke workflow to rebuild the broken service from scratch while preserving data and interfaces.

Frequently Asked Questions about nuke

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

FAQPage Schema
How do I safely rebuild a broken service from scratch without losing data?

Safely rebuild a broken service by backing up databases and configuration first, then orchestrating a parallel component rebuild and running acceptance tests before cutover to preserve data and interfaces.

What is the best way to fix unfixable technical debt in a production service?

Fix unfixable technical debt through a controlled teardown that scaffolds a fresh replacement architecture, preserving the old version for rollback until the new build passes pre-cutover validation.

How do I migrate data when replacing a corrupted service architecture?

Migrate data during a service rebuild by backing up state before teardown, scaffolding the fresh implementation, and migrating existing data into the new build before running integration checks.

Can I preserve API contracts and webhooks when tearing down and rebuilding a service?

Yes, you can preserve API contracts and webhooks during a service rebuild by maintaining the same URLs and MCP tool interfaces so downstream clients keep working without interruption.

When should I consider tearing down a service instead of patching it?

Consider tearing down a service instead of patching when facing recurring configuration corruption, architecture gaps preventing required features, or escalating tech debt that makes reliable fixes impossible.

Does infrastructure automation for service rebuilds require rollback readiness?

Yes, infrastructure automation for service rebuilds requires mandatory rollback readiness, keeping old versions available until the new build passes acceptance testing and traffic is safely switched.