cli-audit-tangle

Analyze codebases for god functions, circular dependencies, dead code, and module boundaries.

5|1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/Destynova2/cli-code-skills --skill cli-audit-tangle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-audit-tangle
Source: https://github.com/Destynova2/cli-code-skills/tree/main/cli-audit-tangle
Command: npx skills add https://github.com/Destynova2/cli-code-skills --skill cli-audit-tangle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cargo, pyan3, madge, go-callvis, ast-grep, pydeps, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill analyzes codebase structure and identifies issues such as god functions, circular dependencies, dead code, and suboptimal module boundaries, helping to refactor code and improve maintainability.

Core Features & Use Cases

  • Code Structure Analysis: Identifies structural problems in codebases that are not visible to linters.
  • God Function Detection: Identifies functions with high coupling, indicating potential refactoring opportunities.
  • Circular Dependency Detection: Detects circular dependencies that can cause runtime issues.
  • Dead Code Detection: Identifies dead code that can be removed, improving code maintainability.
  • Module Boundary Analysis: Suggests improvements for module boundaries to reduce coupling and improve cohesion.
  • CI/CD Pipeline Analysis: Analyzes CI/CD pipeline dependencies and detects deadlocks and bottlenecks.
  • Use Case: When reviewing a large codebase and needing to understand the structural complexity and identify areas for refactoring.

Quick Start

Analyze the code structure in the 'src/' directory of your project.

Frequently Asked Questions about cli-audit-tangle

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

FAQPage Schema
How do I detect circular dependencies and spaghetti code in my codebase?

To detect circular dependencies and spaghetti code, static code analysis is performed to identify structural issues like god functions, dead code, and suboptimal module boundaries. This requires language-specific analysis tools to map dependencies.

What is the best way to analyze code structure for refactoring opportunities?

Analyzing code structure for refactoring involves identifying god functions with high coupling and dead code. This approach goes beyond standard linters by uncovering deep structural problems and suggesting improvements for module boundaries to increase cohesion.

Do I need specific dependency analysis tools to check for dead code in different languages?

Yes, you need specific dependency analysis tools to check for dead code in different languages. The analysis requires tools specific to your codebase's language, utilizing dependencies like madge for JavaScript or pydeps for Python.

Can I use static code analysis to identify bottlenecks in my CI/CD pipeline?

Yes, you can use static code analysis to identify bottlenecks in your CI/CD pipeline. The analysis examines pipeline dependencies to detect deadlocks and structural bottlenecks that can slow down deployments.

How do I find god functions causing high coupling in a large project?

Finding god functions causing high coupling requires static code analysis that identifies functions with excessive dependencies. This highlights code areas needing immediate refactoring to reduce complexity and improve maintainability.

Does code structure analysis work for identifying suboptimal module boundaries?

Yes, code structure analysis works for identifying suboptimal module boundaries by evaluating how modules interact. It suggests improvements to reduce coupling and improve overall cohesion across your codebase.