Get the FREE Ultimate OpenClaw Setup Guide →

Matrix Nuke

npx machina-cli add skill ojowwalker77/Claude-Matrix/nuke --openclaw
Files (1)
SKILL.md
5.9 KB

Matrix Nuke

Comprehensive codebase hygiene analysis. Detects dead code, unused imports, orphaned files, circular dependencies, stale TODOs, unnecessary comments, overengineered dependencies, and more across 11 categories.

Tip: This skill runs in a forked context for unbiased analysis - clean slate, no conversation history bias.

Architecture

ORCHESTRATOR (parse mode, dispatch agents, aggregate report)
     |
     +-- STRUCTURAL AGENT --> dead exports, orphaned files, unused imports
     +-- CIRCULAR DEP AGENT --> import cycle detection
     +-- DEPENDENCY AGENT --> unused npm packages, overengineered deps
     +-- GENERATIVE AGENT --> comments, console.log, copy-paste, TODOs
     +-- TRIAGE AGENT --> confidence scoring, safety filtering, tiering

Usage

Parse user arguments from the skill invocation (text after the trigger phrase).

Expected format: /nuke [mode] [path]

Modes

ModeCommandBehavior
Scan/nuke or /nuke scanReport only - touch nothing (default)
This/nuke this <file>Single file analysis
Safe/nuke safeReport HIGH confidence only (>90%)
Aggressive/nuke aggressiveReport MEDIUM+ confidence (>70%)

Path Filtering

Append a path to any mode to limit scope:

  • /nuke scan src/api/ - only scan src/api/
  • /nuke this src/utils/auth.ts - single file

Examples

/nuke                        # Full scan, report only
/nuke scan                   # Same as above
/nuke this src/utils/auth.ts # Single file analysis
/nuke scan src/api/          # Scan specific directory
/nuke safe                   # High-confidence findings only
/nuke aggressive             # Medium+ confidence findings

Pipeline

Follow the orchestration detailed in references/nuke-pipeline.md:

  1. Pre-flight - Check index availability (matrix_index_status), detect entry points from package.json, parse mode
  2. Structural Analysis - Use matrix_find_dead_code for dead exports + orphaned files
  3. Circular Dep Detection - Use matrix_find_circular_deps for import cycles
  4. Dependency Analysis - Read package.json, cross-reference with actual imports via Grep
  5. Generative Analysis - AI inspection of files for comments, console.log, duplication, TODOs
  6. Triage - Apply safety rules, assign confidence scores, classify into tiers
  7. Report - Generate formatted output per references/output-format.md

Early exit for /nuke this: Only run Structural + Generative agents on that single file. Skip dependency and circular dep analysis.

Graceful degradation: If index is unavailable, fall back to Grep-based analysis. Report reduced accuracy.

What Gets Detected (11 Categories)

Structural (deterministic, via MCP tools)

  1. Dead exports - exported symbols with zero callers across the codebase
  2. Orphaned files - files that nothing imports (excluding entry points)
  3. Circular dependencies - import cycles in the dependency graph
  4. Unused npm packages - in package.json but never imported
  5. Unused imports - imports brought in but never referenced in the file

Generative (AI judgment required)

  1. Unnecessary comments - obvious/redundant comments (// increment i, // constructor)
  2. Commented-out code - dead code hiding in comments (contains {, =, function, return)
  3. Console.log leftovers - console.log and console.debug left from debugging (NOT console.error)
  4. Overengineered deps - libraries replaceable with native APIs (lodash.get -> ?., moment -> Intl)
  5. Copy-paste duplication - near-identical code blocks (5+ similar consecutive lines)
  6. Stale TODO/FIXME - ancient TODOs with no linked issues and old git blame dates

Safety Rules

See references/safety-rules.md for full details. Key rules:

  • Never flag entry points - index.ts, main.ts, bin/*, package.json main/module/exports
  • Never flag framework conventions - pages/, routes/, app/, .config., migrations/
  • Never flag dynamically imported modules - import(), require() references
  • Never flag public API surface - root barrel exports, @public JSDoc
  • Respect .nukeignore - if present, honor it like .gitignore

Additional Resources

  • references/nuke-pipeline.md - Full orchestrator pipeline
  • references/agents/structural-agent.md - Dead code detection via MCP tools
  • references/agents/generative-agent.md - AI-judged detection patterns
  • references/agents/dependency-agent.md - Package analysis and native alternatives
  • references/agents/triage-agent.md - Confidence scoring and safety filtering
  • references/safety-rules.md - Entry point detection, what NOT to flag
  • references/output-format.md - Report template

Source

git clone https://github.com/ojowwalker77/Claude-Matrix/blob/main/skills/nuke/SKILL.mdView on GitHub

Overview

Matrix Nuke performs comprehensive codebase hygiene across 11 categories, detecting dead code, unused exports, orphaned files, circular dependencies, stale TODOs, unnecessary comments, overengineered dependencies, and more. It runs in a forked context to ensure unbiased analysis for safe cleanup.

How This Skill Works

An orchestrator coordinates five specialized agents (Structural, Circular Dep, Dependency, Generative, and Triage) to surface issues and assemble a structured report. It relies on Matrix MCP tools (dead code, circular deps, exports, imports, and search utilities) and can fall back to Grep if the index is unavailable. Modes like Scan, This, Safe, and Aggressive, plus optional path filters, control scope and depth.

When to Use It

  • Kick off a full codebase cleanup before a major release to reduce dead code and bloated imports
  • After a refactor to surface orphaned files, dead exports, and circular dependencies
  • Audit for unused npm packages and overengineered dependencies to shrink the footprint
  • Investigate import cycles in a monorepo and apply targeted fixes
  • Analyze a single file to verify quality, remove unnecessary logs, and prune TODOs

Quick Start

  1. Step 1: Run a full scan with '/nuke' (default) to generate a baseline report
  2. Step 2: Narrow the scope with '/nuke scan <path>' or '/nuke this <file>' as needed
  3. Step 3: Review the report, prune dead code, imports, and packages, then rerun to verify

Best Practices

  • Run in a forked context to avoid history bias and ensure clean baseline
  • Start with a full scan (default mode) before targeted scans of specific files or dirs
  • Cross-check findings with Grep fallback if the index is unavailable or stale
  • Back up results and iterate with staged commits to validate removals
  • Prioritize Safe findings (>90% confidence) before tackling Aggressive findings

Example Use Cases

  • Identify and prune dead exports in a large React/TypeScript project
  • Find orphaned files after a module restructuring and delete or relocate them
  • Detect circular dependencies in a monorepo and refactor import paths
  • Remove unused npm packages to cut installation size and risk surface
  • Clean up console.log statements and TODOs across multiple files

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers