skills.rest
fysoul17
fysoul17COMMUNITY
Explore all skills by this author →
𝕏@0xMcDonAltGitHub

devlyn:clean

Detect dead code, stale tests, and unused dependencies across project structures.

4|Updated Feb 23, 2026
Search Tags:#technical debt#dead code#code cleanup#dependency hygiene#test health#complexity hotspots
One-click install
npx skills add https://github.com/fysoul17/ian-on-v1 --skill devlyn-clean
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devlyn:clean
Source: https://github.com/fysoul17/ian-on-v1/tree/main/ian-on/.claude/skills/devlyn%3Aclean
Command: npx skills add https://github.com/fysoul17/ian-on-v1 --skill devlyn-clean

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reduce maintainability risk by detecting dead code, stale tests, unused dependencies, and complexity hotspots so your codebase stays lean and easier to evolve.

Core Features & Use Cases

  • Dead code detection: Identifies orphan files, unused exports, dead routes, and redundant or commented-out blocks.
  • Dependency hygiene: Finds dependencies and dev tooling that are unused by production code and flags version/duplication bloat.
  • Test health review: Surfaces empty, obsolete, or skipped tests and highlights coverage gaps.
  • Complexity hotspot measurement: Flags overly large or deeply nested modules and god-object-like accumulations of responsibility.
  • Code hygiene improvements: Detects console/logging issues, long-lived TODO/FIXME, magic numbers, duplication, empty catches, and problematic type patterns.

Quick Start

Run devlyn:clean with an optional focus area to audit your repository and propose a prioritized cleanup plan for safe execution.

Frequently Asked Questions about devlyn:clean

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

FAQPage Schema
How do I find and remove dead code in a TypeScript or Python project?▼

To find and remove dead code, audit your TypeScript or Python project to detect orphan files, unused exports, and dead routes, generating a prioritized cleanup report with risk levels.

What is the best way to identify unused dependencies and reduce bloat?▼

Identifying unused dependencies involves scanning your codebase to find packages unused by production code and flagging version or duplication bloat, resulting in a safer dependency hygiene cleanup plan.

How do I clean up stale tests and find coverage gaps in my codebase?▼

Cleaning up stale tests requires a test health review to surface empty, obsolete, or skipped tests and highlight coverage gaps, producing a prioritized list of test issues to resolve safely.

Can I audit complexity hotspots and technical debt across different programming languages?▼

Yes, you can audit complexity hotspots and technical debt across typical Node, Rust, Go, and other project structures to flag overly large modules and god-object accumulations for team resolution.

How safely are code cleanup changes applied when reducing technical debt?▼

Code cleanup changes are applied safely by producing a P0–P3 prioritized risk report and executing only user-approved changes in a defined safe order to prevent breaking modifications.

Related Skills

Explore More Software Engineering Skills→
OrestesKOrestesK
2

learn-codebase

Analyze project instructions, structure, dependencies, and workflows to orient developers.

Community
Intermediate
artivillaartivilla

knip

Detect unused files, dependencies, and exports in JavaScript/TypeScript projects.

Community
Advanced
mthinesmthines
7

review-changes

Analyze code diffs and documentation updates to identify quality issues.

Community
Intermediate
abnegateabnegate
2

cleanup

Remove dead code and unused imports from Kotlin codebases without changing behavior.

Community
Advanced