codebase-memory-quality

Identify dead code and high-cost functions using graph-based queries.

5|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/sambeau/kanbanzai --skill codebase-memory-quality-sambeau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-memory-quality
Source: https://github.com/sambeau/kanbanzai/tree/main/.github/skills/codebase-memory-quality
Command: npx skills add https://github.com/sambeau/kanbanzai --skill codebase-memory-quality-sambeau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify dead code and underperforming functions in a codebase, enabling targeted cleanups and more maintainable software.

Core Features & Use Cases

  • Dead code detection: find functions with zero inbound callers.
  • Refactor candidates: surface high fan-out/in functions for consolidation or decomposition.
  • Cross-file coupling insights: reveal modules with tight interdependencies that hinder changes.
  • Use Case: When revising a legacy system, run the analysis to surface dead branches and refactor hotspots for safer upgrades.

Quick Start

Run the analysis to locate dead code, surface refactor candidates, and review the results.

Frequently Asked Questions about codebase-memory-quality

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

FAQPage Schema
How do I find and remove dead code in a large codebase?

To find dead code, this analysis scans your codebase using graph-based queries to identify functions with zero inbound CALLS edges, pinpointing unused branches for safe removal and maintainability improvements.

What is the best way to identify refactor candidates with high fan-out or fan-in?

Refactor candidates are identified by analyzing function call graphs to surface high fan-out or fan-in functions, guiding targeted consolidation or decomposition to reduce complexity in your software.

Can I use static analysis to detect cross-file coupling and unused functions?

Static analysis reveals cross-file coupling and unused functions by mapping function call dependencies across modules, highlighting tight interdependencies and zero-caller functions that hinder codebase changes.

Does this dead code discovery work for large legacy systems across different programming languages?

Dead code discovery is applicable to large and evolving software projects across languages, helping triage unused functions and refactor hotspots for safer upgrades when revising legacy systems.

When should I use graph analysis for code quality instead of standard static analysis?

Graph analysis is needed when you want to reveal structural insights like zero inbound function calls, high fan-out or fan-in, and cross-file coupling, going beyond standard checks to guide targeted refactoring.