skills.rest
bmsull560
bmsull560COMMUNITY
Explore all skills by this author →
GitHub

dead-code-sweeper

Identify and remove dead code with dependency analysis and safe removal patches.

Updated Apr 8, 2026
Search Tags:#frontend#backend#static-analysis#dead-code#code-cleanup#refactor-cleanup#safety-patches
One-click install
npx skills add https://github.com/bmsull560/Fabric_4L --skill dead-code-sweeper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dead-code-sweeper
Source: https://github.com/bmsull560/Fabric_4L/tree/main/.windsurf/skills/dead-code-sweeper
Command: npx skills add https://github.com/bmsull560/Fabric_4L --skill dead-code-sweeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies dead code across frontend and backend codebases, including orphan pages, unreachable routes, unused exports, mock data blocks, and duplicate workspace systems. Verifies reachability and produces safe removal patches with dependency analysis to minimize risk.

Core Features & Use Cases

  • Detects dead code in UI and server layers, including frontend routes, components, and backend utilities.
  • Validates reachability before proposing removals and generates patch-ready changes with dependency traces.
  • Ideal for post-refactor cleanups, ongoing code hygiene, and audit-driven remediations.

Quick Start

Run the dead-code sweep to identify and safely patch dead code across the codebase.

Frequently Asked Questions about dead-code-sweeper

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

FAQPage Schema
How do I find and safely remove dead code after a frontend and backend refactor?▼

Dead code cleanup validates reachability across frontend routes, components, and backend utilities before proposing removals. It generates patch-ready changes with dependency analysis to ensure safe extraction.

What is static analysis for dead code detection and how does it work?▼

Static analysis for dead code detects unreachable routes, unused exports, and mock data blocks across UI and server layers. It verifies reachability and produces safe removal patches with dependency traces.

Can I use dead code sweeping for ongoing code hygiene in both frontend and backend codebases?▼

Dead code sweeping supports ongoing hygiene and audit-driven remediations across frontend and backend codebases. It detects unused exports and orphan pages, producing patch-ready changes with dependency analysis.

What's the best way to generate safe removal patches for unreachable routes and unused exports?▼

Generating safe removal patches requires validating reachability of unreachable routes and unused exports first. This produces patch-ready changes with dependency traces, minimizing risk during extraction.

Does dead code detection work for mock data blocks and duplicate workspace systems?▼

Dead code detection identifies mock data blocks and duplicate workspace systems by analyzing reachability across frontend and backend layers. It generates safety patches with dependency analysis for secure removal.

Related Skills

Explore More Software Engineering Skills→
watminwatmin

purgare

Detect dead code patterns and surface refactoring signals in codebases.

Community
Advanced
rob-broadleyrob-broadley

dead-code-review

Detect unreachable code, unused exports, orphaned files, and stale feature flags.

Community
Advanced
BamoseBamose
5

refactor-cleaner

Detect dead code and unused exports in TypeScript projects with knip, depcheck, and ts-prune.

Community
Advanced
quangphu1912quangphu1912
1

detecting-dead-code

Identify and classify dead code, unused exports, and orphaned files in a codebase.

Community
Intermediate