code-maintenance

Audits a repository for junk files, stale docs, and dead code, then produces an incremental cleanup plan.

96|11|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/thefrederiksen/devthrottle --skill code-maintenance-thefrederiksen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-maintenance
Source: https://github.com/thefrederiksen/devthrottle/tree/main/.claude/skills/code-maintenance
Command: npx skills add https://github.com/thefrederiksen/devthrottle --skill code-maintenance-thefrederiksen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories accumulate cruft over time: garbage-named files, stale handover and plan documents, unreferenced projects, and leftover archived directories. Removing everything at once is risky, so this Skill audits the repo read-only, classifies every finding, and produces an incremental, one-issue-at-a-time cleanup plan. ## Core Features & Use Cases - Whole-repo hygiene audit: Scans tracked files for junk names, root clutter, stale docs, dead C# projects, and undecided archived directories. - Classified findings: Tags each finding as DELETE, ARCHIVE, MOVE, KEEP, or UNSURE with a LOW/MEDIUM/HIGH risk level. - Approval-gated GitHub issues: Files one epic plus one child issue per work unit with the maintenance label, each stating what to remove, how to verify, and how to roll back. - Use Case: After a large feature lands, run the audit to find 3 corrupted filenames, an empty test project, and 20 stale handover docs, then file ordered cleanup issues so a developer removes each item with a green build between steps. ## Quick Start Ask the agent to clean up the repo and it will run the audit checklist and return a categorized cleanup plan for your approval.

Frequently Asked Questions about code-maintenance

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

FAQPage Schema
How do I clean up a cluttered git repository safely?▼

Run a read-only audit that classifies each finding as DELETE, ARCHIVE, MOVE, KEEP, or UNSURE, then remove items one GitHub issue at a time with a build and test run between removals. This incremental approach makes it possible to identify what broke if something fails.

How to find dead or unreferenced C# projects in a solution?▼

Compare each src directory against the .sln file, check for empty project dirs with no tracked source, and verify whether any other project's .csproj references it or any code uses its namespace. Confirm no reflection or DI runtime loading before recommending deletion.

Does the code-maintenance skill delete files automatically?▼

No, it never deletes, moves, or rewrites code on its own. It produces a categorized report and, only with explicit approval, files GitHub issues; actual removal is done by a developer working one issue at a time.

What should I do with stale handover and plan documents?▼

Archive completed handover, plan, and tracker documents under docs/archive/<category>/ with a short README noting provenance. Keep the live docs tree limited to current reference material and active plans.

Why is a file named nul dangerous in a Windows git repo?▼

nul is a Windows reserved device name that breaks git operations on Windows, so it should be deleted immediately when found. It typically appears from a botched shell redirect and is always safe to remove.