legacy-purge

Name: legacy-purge
Availability: InStock
Author: dawn840705

Audit codebases for legacy residue and generate categorized review reports.

Updated Aug 27, 2026

Search Tags:#audit #migration #cleanup #grep #policy #legacy #code-residue

Ready to run

npx skills add https://github.com/dawn840705/claude-code-studios --skill legacy-purge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: legacy-purge
Source: https://github.com/dawn840705/claude-code-studios/tree/main/skills/legacy-purge
Command: npx skills add https://github.com/dawn840705/claude-code-studios --skill legacy-purge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit codebases to identify legacy residue left after pivots, migrations, or deprecations, enabling safe cleanup decisions.

Core Features & Use Cases

Residue categorization: Detects deprecated files, stale configs, archive paths, and legacy docs.
Policy-aware results: Classifies findings using project deprecation policies and outputs a human-review report.
Use Case: After a major migration, run the audit to surface dead-weight assets and guide retention decisions.

Quick Start

Run a full legacy residue audit on the current codebase and generate a categorized report of suspect files and patterns.

Frequently Asked Questions about legacy-purge

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

FAQPage Schema

How do I audit my codebase for legacy residue after a migration?▼

A legacy residue audit scans code, docs, and config to detect deprecated files and stale patterns after migrations. It cross-references policy documents and outputs a categorized human-review report to guide safe cleanup decisions.

What is legacy code residue and how do I identify stale configs?▼

Legacy code residue includes deprecated files, stale configs, archive paths, and legacy docs left after pivots or migrations. You identify them by enforcing a predefined residue category checklist that classifies findings based on project deprecation policies.

How do I generate a post-migration cleanup report without deleting files?▼

You generate a post-migration cleanup report by running an audit that catalogs dead-weight assets and legacy residue. The audit enforces a predefined checklist and outputs a categorized review report, ensuring no files are actually deleted during the process.

Does the legacy residue audit work with my existing deprecation policy documents?▼

Yes, the legacy residue audit is policy-aware and cross-references your existing deprecation policy documents. It classifies detected legacy code residue according to these predefined policies to help reviewers make accurate retention decisions.

What is the best way to classify dead-weight assets and deprecated files after a pivot?▼

The best way to classify dead-weight assets and deprecated files after a pivot is to use a policy-aware audit. It detects archive paths and legacy docs, enforcing a residue category checklist to output a structured triage report for reviewers.

Are there limitations to using automated codebase cleanup for detecting legacy docs?▼

A key limitation of this codebase cleanup approach is that it strictly outputs a human-review report and does not automatically delete legacy docs or deprecated files. Reviewers must manually triage findings to enforce retention decisions.