ss-simplify-repo

Audit repositories for dead code, outdated dependencies, and unnecessary complexity.

Updated Feb 14, 2026

Search Tags:#code quality #refactoring #dependency management #code audit #tech debt #dead code

Ready to run

npx skills add https://github.com/JasonLo/skill-sommelier --skill ss-simplify-repo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ss-simplify-repo
Source: https://github.com/JasonLo/skill-sommelier/tree/main/skills/ss-simplify-repo
Command: npx skills add https://github.com/JasonLo/skill-sommelier --skill ss-simplify-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill tackles the issue of overgrown and complex codebases by systematically identifying and proposing the removal of unnecessary elements like dead code, over-engineered abstractions, and outdated dependencies.

Core Features & Use Cases

Complexity Audit: Analyzes repositories for structural issues, dead code, and code complexity.
Dependency Check: Identifies unused or outdated dependencies and suggests removals.
Configuration Cleanup: Flags stale configurations and boilerplate code.
Use Case: After a major feature merge, use this Skill to ensure no cruft was left behind, making the codebase leaner and easier to maintain.

Quick Start

Run ss-simplify-repo to audit the current repository for unnecessary complexity and propose simplifications.

Frequently Asked Questions about ss-simplify-repo

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

FAQPage Schema

How do I audit my codebase for dead code and unnecessary complexity?▼

To audit your codebase for dead code and complexity, you can run this Skill to systematically analyze repositories for structural bloat, over-engineered abstractions, and propose concrete simplifications.

What is the best way to find unused dependencies and outdated packages in my repository?▼

The best way to find unused dependencies is through a dependency check that identifies outdated or unused packages and suggests removals to make your codebase leaner and easier to maintain.

How do I clean up stale configurations and boilerplate code after a major feature merge?▼

To clean up stale configurations and boilerplate code after a major feature merge, perform a configuration cleanup audit to flag and remove cruft left behind during development.

Can I detect overengineering and stale TODOs in a codebase that has undergone recent refactoring?▼

Yes, you can detect overengineering and stale TODOs in a recently refactored codebase by executing parallel file reads and searches to systematically analyze complexity and identify unnecessary abstractions.

Does this dead code detection approach work for repositories suspected of containing tech debt?▼

Yes, this dead code detection approach works for repositories with tech debt by applying systematic complexity analysis, dependency auditing, and configuration review to identify and propose removing unnecessary elements.