kanso-nuclear

Audit repository structure to identify file sprawl and abstraction issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the accumulation of structural technical debt, such as file sprawl, spaghetti code, and abstraction theatre, which standard audits often overlook.

Core Features & Use Cases

  • Structural Audit: Performs a deep, maintainability-focused sweep of the codebase to identify architectural weaknesses.
  • Judo Simplification: Prioritizes the deletion of complex logic and unnecessary abstractions over simple refactoring.
  • Use Case: Use this when a codebase has become difficult to reason about or when a PR introduces significant structural complexity that threatens long-term maintainability.

Quick Start

Run the kanso-nuclear skill on the current branch to perform a deep structural audit of all modified files.

Frequently Asked Questions about kanso-nuclear

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

FAQPage Schema
How do I audit my codebase for structural technical debt and file sprawl?

To audit structural technical debt, you need a tool that analyzes repository architecture to identify maintainability issues like file sprawl and spaghetti growth. This skill performs a rigorous structural audit across entire repositories or specific paths to enforce architectural standards.

What is the best way to find unnecessary abstractions and complexity in a git diff?

Finding unnecessary abstractions in a git diff requires analyzing modified files for abstraction theatre and spaghetti growth. You can run a structural audit on the current branch to identify high-leverage simplification opportunities and prioritize deleting complex logic over simple refactoring.

How does a structural code audit identify maintainability issues?

A structural code audit identifies maintainability issues by analyzing repository structure using standard utilities like git, grep, and find. It scans for architectural weaknesses such as file sprawl, spaghetti code, and abstraction theatre that threaten long-term maintainability.

Can I use standard command line tools to check code architecture quality?

Yes, you can check code architecture quality using standard command line tools. This approach requires git, grep, and find utilities to analyze repository structure and identify high-leverage simplification opportunities without needing complex external dependencies.

When should I run a maintainability audit on my codebase?

You should run a maintainability audit when your codebase has become difficult to reason about or when a pull request introduces significant structural complexity. This deep structural sweep identifies architectural weaknesses and enforces strict standards.

What is judo simplification for code refactoring?

Judo simplification in code refactoring prioritizes the deletion of complex logic and unnecessary abstractions over simple refactoring. It targets high-leverage simplification opportunities to eliminate maintainability issues like spaghetti growth and abstraction theatre.