skills.rest
langcore-org
langcore-orgCOMMUNITY
Explore all skills by this author →
GitHub

feature-cleanup

Identify unused code and guide approval-based deletion workflows.

1|Updated Oct 27, 2025
Search Tags:#refactoring#technical debt#code audit#code cleanup#unused code#feature removal
One-click install
npx skills add https://github.com/langcore-org/united-productions-web --skill feature-cleanup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-cleanup
Source: https://github.com/langcore-org/united-productions-web/tree/main/.claude/skills/feature-cleanup
Command: npx skills add https://github.com/langcore-org/united-productions-web --skill feature-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @supabase/supabase-js, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you safely identify, analyze, and remove unused features and code from your codebase, reducing technical debt and improving maintainability.

Core Features & Use Cases

  • Automated Discovery: Finds unused directories, files, and code references.
  • Risk Assessment: Analyzes the potential impact of removing a feature.
  • Guided Deletion: Provides a step-by-step, approval-based workflow for safe removal.
  • Use Case: Regularly clean up your codebase by identifying and removing features that are no longer needed, preventing the accumulation of dead code and reducing build times.

Quick Start

Use the feature-cleanup skill to audit for unused features and initiate a guided deletion process.

Frequently Asked Questions about feature-cleanup

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

FAQPage Schema
How do I safely identify and remove unused code from my codebase?▼

To safely remove unused code, this Skill automates the discovery of unused directories, files, and references, then provides an approval-based guided deletion workflow to ensure safe technical debt reduction.

What is the best way to assess the risk of removing a feature?▼

Risk assessment for feature removal is handled by analyzing the potential impact of deleting unused code, allowing developers to evaluate dependencies and prevent breaking changes before proceeding with any deletion.

Can I automate technical debt reduction without manual approval?▼

No, automated technical debt reduction requires careful human oversight and approval for all deletion actions, ensuring that the guided deletion of unused features remains safe and controlled.

Does the code cleanup process require a database dependency?▼

Yes, the code cleanup process uses the Supabase JavaScript client as a dependency to support script-based analysis and database cleanup for identifying and removing unused features.

When do I need to perform a code audit for dead code?▼

You need a code audit for dead code when your project accumulates unused features, which reduces maintainability and increases build times, requiring script-based analysis to identify technical debt.

Are there limitations to using automated scripts for feature removal?▼

Automated scripts for feature removal are limited by their dependency on human approval for deletions, meaning interactive workflows and manual oversight are required to prevent accidental removal of active code.

Related Skills

Explore More Software Engineering Skills→
quangphu1912quangphu1912
1

detecting-dead-code

Identify and classify dead code, unused exports, and orphaned files in a codebase.

Community
Intermediate
matteocervellimatteocervelli
25

rust-quality-checker

Run rustfmt, clippy, cargo check, test, and audit for Rust quality gates.

Community
Advanced
edulazaroedulazaro
12

lc:orphaned-records

Detect and remediate orphaned database records in Laravel environments.

Community
Advanced
DayoptDayopt

cleanup

Detect and remove unused code, dead imports, and console statements in TypeScript/JavaScript projects.

Official
Advanced