dead-code-finder

Detect unused projects, files, XAML components, and services in the CC Director C# codebase.

94|11|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/thefrederiksen/cc-director --skill dead-code-finder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dead-code-finder
Source: https://github.com/thefrederiksen/cc-director/tree/main/.claude/skills/dead-code-finder
Command: npx skills add https://github.com/thefrederiksen/cc-director --skill dead-code-finder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and remove unused code, projects, and components within the CC Director application, leading to a cleaner, more maintainable, and efficient codebase.

Core Features & Use Cases

  • Unused Project Detection: Identifies .csproj files that are not referenced by any other project and are not entry points.
  • Unused File Detection: Finds C# files with public classes or interfaces that have zero external references and are not entry points or test files.
  • Unused XAML Detection: Locates XAML files (UserControls, Windows) that are never instantiated or referenced elsewhere.
  • Unused Service Detection: Identifies services registered in dependency injection that are never used.
  • Use Case: Before a major refactor, use this Skill to pinpoint areas of the codebase that can be safely removed, reducing technical debt and simplifying future development.

Quick Start

Run the dead-code-finder skill to analyze the CC Director project for unused code.

Frequently Asked Questions about dead-code-finder

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

FAQPage Schema
How do I find unused C# code and projects in my codebase?

To find unused C# code, analyze project references, file content, XAML usage, and dependency injection registrations to detect public classes, interfaces, and services with zero external references.

What is the best way to detect unused XAML components before refactoring?

Detecting unused XAML components involves locating UserControls and Windows that are never instantiated or referenced elsewhere in the codebase, ensuring they are safe removal candidates before a major refactor.

How do I identify unused services registered in dependency injection?

Identify unused services in dependency injection by scanning the registration mappings and verifying whether the registered service interfaces are actually resolved or injected anywhere else in the application.

Does this dead code analysis tool work for any C# project?

This specific dead code analysis targets the CC Director C# codebase, examining its unique project references, XAML files, and dependency injection setup to pinpoint potential code removal candidates.

What are the limitations of automated dead code detection in C#?

Automated dead code detection requires manual review and adherence to safety guidelines before any code deletion, because dynamic references or reflection patterns may not be visible to static analysis.

How do I locate orphaned .csproj files that are not entry points?

Locate orphaned .csproj files by analyzing project references to identify assemblies that are not referenced by any other project and are not configured as application entry points.