skills.rest
Hedgehogues
HedgehoguesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dead-features

Audit codebases to identify implemented but user-unreachable features across endpoints, UI, routes, services, and exports.

25|5|Updated Mar 25, 2026
Search Tags:#ui#architecture#routing#static-analysis#code-audit#dead-features
One-click install
npx skills add https://github.com/Hedgehogues/awesome-claude --skill dead-features
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dead-features
Source: https://github.com/Hedgehogues/awesome-claude/tree/main/skills/dead-features
Command: npx skills add https://github.com/Hedgehogues/awesome-claude --skill dead-features

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implemented functionality that never reaches users is a hidden cost; this skill helps auditors locate dead features that are not reachable via UI, routes, or exports, enabling focused cleanup and architectural clarity.

Core Features & Use Cases

  • Discover dead features by cross-checking end-to-end connectivity between endpoints, UI components, routers, services, and exports.
  • Generate a structured table report detailing each dead artifact to guide refactoring and removal.
  • Apply to monorepos or multi-language stacks to improve overall code health and maintainability.

Quick Start

Run the dead-features audit on your repository to produce a consolidated dead features report.

Frequently Asked Questions about dead-features

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

FAQPage Schema
How do I find dead code and unreachable features in my codebase?▼

To find dead code and unreachable features, you audit the project to locate implemented functionality that users cannot reach via UI components, routes, endpoints, or exports. This process performs static code inspection to output a structured report detailing each dead artifact for removal.

What is the best way to audit unreachable endpoints and UI components in a monorepo?▼

The best way to audit unreachable endpoints and UI components in a monorepo is to perform cross-layer connectivity verification across services and routing. This static analysis checks end-to-end connectivity to identify dead features and outputs a consolidated table report.

Can I detect dead features across a multi-language software stack?▼

Yes, you can detect dead features across a multi-language stack by applying static code inspection to verify cross-layer connectivity. The audit identifies user-unreachable exports and services, generating a structured report to guide refactoring across diverse codebases.

How do I generate a dead features report to guide codebase refactoring?▼

You generate a dead features report by running a static code audit that cross-checks connectivity between endpoints, UI components, routers, and services. The resulting structured table details each dead artifact, providing clear targets for codebase refactoring and cleanup.

Why does static analysis fail to find dead routes and services in my project?▼

Static analysis may overlook dead routes and services if it only checks single layers in isolation. Identifying dead features requires cross-layer connectivity verification across endpoints, UI components, and exports to confirm whether functionality is truly user-unreachable.

Related Skills

Explore More Software Engineering Skills→
uukuguyuukuguy
1

code-metrics

Calculate complexity, size, coupling, and duplication metrics from source code.

Community
Intermediate
coreyjacoreyja
6

Global Coding Style

Enforce consistent naming, formatting, and DRY principles across codebases.

Community
Basic
robotijnrobotijn
3

dead-code-detector

Detect unused, unreachable, and orphaned code across 7 programming languages and SQL databases.

Community
Advanced
Obsidian-OwlObsidian-Owl
9

gate-wiring

Detect unused exports, orphaned files, layer violations, and circular dependencies in changed code.

Official
Intermediate