skills.rest
odylith
odylithOFFICIAL
Explore all skills by this author →
GitHub

odylith-code-hygiene-guard

Detect code-hygiene defects in slices and propose cleanup steps.

34|3|Updated Apr 6, 2026
Search Tags:#linting#refactoring#cleanup#code-quality#hygiene#code#modularization
One-click install
npx skills add https://github.com/odylith/odylith --skill odylith-code-hygiene-guard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: odylith-code-hygiene-guard
Source: https://github.com/odylith/odylith/tree/main/.agents/skills/odylith-code-hygiene-guard
Command: npx skills add https://github.com/odylith/odylith --skill odylith-code-hygiene-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain code hygiene by detecting duplicate helpers, fake modularization, oversized-file pressure, and AI-shaped code slop, enabling explicit cleanup discipline.

Core Features & Use Cases

  • Detect duplicate helpers and consolidate logic to reduce redundancy.
  • Identify fake modularization where responsibilities are split without real boundaries.
  • Flag oversized files and AI-shaped code slop, and propose targeted cleanup and refactoring steps.
  • Use Case: When a slice has multiple near-identical helpers or sprawling monolithic modules, run this Guard to surface actionable cleanup tasks and enforcement rules.

Quick Start

Describe the slice you want cleaned and run the hygiene guard to generate a prioritized cleanup plan.

Frequently Asked Questions about odylith-code-hygiene-guard

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

FAQPage Schema
How do I detect duplicate helpers and code redundancy in my software slices?▼

To detect duplicate helpers, you run a hygiene guard on your slices to identify near-identical logic and generate a plan to consolidate it. This surfaces actionable cleanup tasks to eliminate redundant code.

What is fake modularization and how do I identify it in my codebase?▼

Fake modularization is when code responsibilities are split into separate files without establishing real boundaries. You identify it by analyzing your slices to flag components where responsibilities overlap or lack clear separation.

How do I refactor oversized files and AI-shaped code slop in my components?▼

You refactor oversized files and AI-shaped code slop by applying a hygiene guard to flag problematic areas and propose targeted refactoring steps. This generates a prioritized cleanup plan with specific enforcement rules.

Does this code cleanup approach work with any software project structure?▼

This cleanup approach works specifically with software projects where code is organized in slices or components. It focuses on analyzing these distinct boundaries to detect hygiene defects and propose refactoring steps.

Can I get concrete refactoring steps and guardrails for boundary enforcement?▼

Yes, you can get concrete refactoring steps and guardrails by running the hygiene guard on your slices. It proposes targeted cleanup actions and establishes boundary enforcement rules to maintain modular code.

Related Skills

Explore More Software Engineering Skills→
VSF-QC-TTSVSF-QC-TTS

common-architecture-audit

Detect structural duplication, logic leakage, and monolithic components via grep-based searches.

Official
Advanced
mistakeknotmistakeknot
3

interscribe

Audit and refactor CLAUDE.md and AGENTS.md documentation for boundary compliance.

Community
Intermediate
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
DaBigHomieDaBigHomie
1

scrutinize

Review codebases for logic errors, security vulnerabilities, and edge cases.

Community
Advanced