code-housekeeping

Scan codebases for compatibility shims, dead code, and stale artifacts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hack-ink/skills --skill code-housekeeping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-housekeeping
Source: https://github.com/hack-ink/skills/tree/main/code-housekeeping
Command: npx skills add https://github.com/hack-ink/skills --skill code-housekeeping

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify potentially removable code and artifacts like compatibility shims, dead code, or stale configurations, providing an evidence-backed report for safe cleanup.

Core Features & Use Cases

  • Compatibility Shim Detection: Finds code written to support older versions or specific environments.
  • Dead Code Identification: Locates unused modules, functions, commented-out blocks, or unreachable code.
  • Stale Artifact Reporting: Flags outdated documentation, scripts, or configuration files.
  • Use Case: A project has been around for years, and you suspect much of the older code is no longer necessary. This Skill will scan the codebase and provide a prioritized list of what can likely be removed, along with the evidence for each finding.

Quick Start

Use the code-housekeeping skill to scan the current repository for dead code and compatibility shims.

Frequently Asked Questions about code-housekeeping

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

FAQPage Schema
How do I find dead code and compatibility shims in my codebase?

Compatibility shims are detected by searching for version-gated logic and keywords written to support older environments, generating an evidence-backed report of removable code candidates.

What is the best way to identify stale artifacts and unused modules for code cleanup?

Code cleanup candidates are identified by scanning for unreferenced symbols, suppressed unused warnings, and stale artifacts, producing a prioritized removal list with supporting evidence.

Can I use static analysis to safely remove old compatibility shims?

Static analysis detects compatibility shims by searching for version-gated logic and environment-specific blocks, producing evidence-backed reports that justify safe code cleanup.

How do I scan a repository for commented-out blocks and unreferenced symbols?

Scanning for unreferenced symbols and commented-out blocks requires static analysis and text search tools to detect removable code and output an evidence-backed cleanup report.

Does code housekeeping work without external dependencies?

Code housekeeping has no external dependencies, but requires static analysis and text search tools to scan codebases and produce evidence-backed cleanup reports.