skills.rest
jmagly
jmaglyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

cleanup-audit

Identify dead code, unused exports, orphaned files, and stale manifest entries.

175|26|Updated Aug 14, 2025
Search Tags:#refactoring#technical debt#code audit#dead code#code cleanup#unused dependencies
One-click install
npx skills add https://github.com/jmagly/aiwg --skill cleanup-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cleanup-audit
Source: https://github.com/jmagly/aiwg/tree/main/agentic/code/frameworks/sdlc-complete/skills/cleanup-audit
Command: npx skills add https://github.com/jmagly/aiwg --skill cleanup-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and reports on various forms of code rot within a codebase, such as dead code, unused exports, orphaned files, stale manifest entries, and unused dependencies, helping to maintain code health and reduce technical debt.

Core Features & Use Cases

  • Dead Code Identification: Pinpoints functions or variables that are exported but never imported.
  • Orphaned File Detection: Finds files that are not reachable from any entry point in the project.
  • Dependency Auditing: Lists dependencies in package.json that are not imported in the codebase.
  • Manifest Verification: Checks for entries in manifest.json files that point to non-existent files.
  • Use Case: Before a major refactor, run this skill to get a clear picture of all the code and dependencies that can be safely removed, streamlining the refactoring process.

Quick Start

Run the cleanup-audit skill to find all unused exports and orphaned files in the current project.

Frequently Asked Questions about cleanup-audit

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

FAQPage Schema
How do I find dead code and unused dependencies in my project?▼

To find dead code and unused dependencies, you can run an audit that analyzes project structure and import graphs to pinpoint exported functions that are never imported and list dependencies in package.json that are not used in the codebase.

What is the best way to detect orphaned files before a major refactoring?▼

Detecting orphaned files before refactoring involves analyzing your project's entry points to find files that are completely unreachable, providing a structured report with confidence-rated findings to ensure safe removal.

Can I automatically fix stale manifest entries pointing to non-existent files?▼

Yes, you can fix stale manifest entries pointing to non-existent files using interactive fixing options, which verify your manifest.json entries and allow you to safely clean up the invalid references.

Does the code audit support filtering results by file scope and issue type?▼

Yes, the code audit supports filtering results by scope and type, allowing you to narrow down the structured report to focus exclusively on specific categories like dead code or unused exports.

How do I get a JSON output of unused exports for my CI/CD pipeline?▼

You can get a JSON output of unused exports by enabling JSON output options during the audit, generating a structured report of confidence-rated findings that can be consumed directly by your CI/CD pipeline.

Related Skills

Explore More Software Engineering Skills→
Michae2xlMichae2xl

codebase-onboarding

Analyze a codebase to generate an onboarding guide with architecture and entry points.

Community
Advanced
gaoqiongxiegaoqiongxie
1

codebase-inventory-audit

Audit codebases to detect orphan code, duplicate logic, and documentation gaps.

Community
Intermediate
NabilThangeNabilThange
1

lint-and-validate

Automate linting and static analysis for Node.js, Python, and TypeScript code.

Community
Intermediate
jcsoftdevjcsoftdev

tree-shaking

Remove unused exports from JavaScript ES module bundles during build time.

Community
Intermediate