codebase-hygiene

Detect semantic duplicates and shallow modules in codebases.

11|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/romiluz13/auto-pi --skill codebase-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-hygiene
Source: https://github.com/romiluz13/auto-pi/tree/main/skills/codebase-hygiene
Command: npx skills add https://github.com/romiluz13/auto-pi --skill codebase-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify bloated codebases where semantic duplicates and unnecessary wrapper modules increase maintenance costs, inconsistency, and navigation complexity without making changes itself.

Core Features & Use Cases

  • Semantic Duplicate Detection: Catalog exported functions, group them by domain, and compare their implementations to find code serving the same intent under different names.
  • Module Deepening Analysis: Identify thin wrappers and pass-through layers that add complexity without meaningful responsibility.
  • Refactoring Guidance: Produce evidence-based findings with recommended fixes while requiring tests, caller updates, and a clean rerun before consolidation.
  • Use Case: Before a refactor, audit utility, validation, formatting, and API-shaping code to find duplicated behavior and shallow abstractions that should be consolidated or deepened.

Quick Start

Use the codebase-hygiene skill to audit this repository for semantic duplicates and shallow modules, then report prioritized findings without modifying files.

Frequently Asked Questions about codebase-hygiene

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

FAQPage Schema
How do I detect semantic duplicates in a codebase before refactoring?

Detect semantic duplicates by cataloging exported functions, grouping them by domain, and comparing implementations to find code serving the same intent under different names during a pre-refactoring audit.

What is the best way to identify shallow modules and thin wrapper layers?

Identify shallow modules by analyzing module responsibilities to detect thin wrappers and pass-through layers that add navigation complexity without providing meaningful functionality or domain logic.

How does a code quality audit handle consolidation safeguards for refactoring?

Code quality audits require consolidation safeguards covering test updates, caller modifications, and a clean post-change validation rerun before consolidating duplicated logic or removing shallow abstractions.

Can I use static analysis to find bloated utility logic without modifying files?

Yes, static analysis can audit utility, validation, and formatting code to produce prioritized findings with file and line references for bloated logic without modifying any repository files.

When do I need a module deepening analysis for my repository?

You need module deepening analysis when wrapper layers and utility logic become bloated, increasing maintenance costs and inconsistency without adding meaningful responsibility to the codebase architecture.