skills.rest
Hedgehogues
HedgehoguesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

remove-feature

Trace feature dependencies and generate a minimal deletion plan.

25|5|Updated Mar 25, 2026
Search Tags:#code-editing#plan-generation#dependency-tracing#claude-ai#feature-removal#tests-adaptation
One-click install
npx skills add https://github.com/Hedgehogues/awesome-claude --skill remove-feature-hedgehogues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: remove-feature
Source: https://github.com/Hedgehogues/awesome-claude/tree/main/skills/remove-feature
Command: npx skills add https://github.com/Hedgehogues/awesome-claude --skill remove-feature-hedgehogues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates surgical removal of a feature by tracing its full dependency graph and building a minimal deletion plan.

Core Features & Use Cases

  • Traces dependencies across UI, backend, and tests to guide removal.
  • Classifies affected code into DELETE/EDIT/ADAPT with minimal disruption.
  • Coordinates tracing, planning, and test adaptation to ensure a safe removal.

Quick Start

Provide the feature name to remove, then run the guided tracing, planning, and test-adaptation workflow to complete the removal.

Frequently Asked Questions about remove-feature

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

FAQPage Schema
How do I safely remove a feature from a large codebase without breaking existing routes and tests?▼

To safely remove a feature, you need to trace its full dependency graph across UI, backend, and tests. This skill classifies affected code into DELETE, EDIT, and ADAPT actions, generating a minimal deletion plan that ensures safe removal with minimal disruption.

What is the best way to trace dependencies for dead code removal across UI and database layers?▼

Tracing dependencies for dead code removal requires identifying all tied files, functions, routes, and components. This skill coordinates multi-layer impact tracing from UI to DB, guiding the deletion planning and test adaptation process.

Can I use this feature removal workflow to deprecate backend functionality and adapt existing tests?▼

Yes, you can use this workflow to deprecate backend functionality. It coordinates tracing, planning, and test adaptation using dedicated flows, ensuring that all tests tied to the deprecated feature are correctly adapted or removed.

How do I plan code edits and deletions when cleaning up deprecated functionality?▼

Planning code edits and deletions involves classifying affected code into DELETE, EDIT, and ADAPT categories. This skill generates a minimal deletion plan along the critical path, coordinating execution and test adaptation to clean up deprecated functionality safely.

Does this dependency tracing approach work for multi-layer codebases spanning from UI to DB?▼

Yes, this dependency tracing approach works for multi-layer codebases. It explicitly covers the full impact from UI to DB, identifying all tied files, functions, routes, and components to build a comprehensive and safe removal plan.

Related Skills

Explore More Software Engineering Skills→
InditexTechInditexTech
195

zoom-out

Generate a high-level module-to-caller map aligned to the domain glossary.

Official
Intermediate
TechyParkTechyPark

safe-file-deletion

Require explicit user permission before deleting files or directories.

Community
Basic
jrmatherlyjrmatherly
1

serena-impact-analysis

Analyze blast radius of port interface changes across codebases.

Community
Intermediate
hawkyrehawkyre
30

remove-code

Trace dependencies and execute isolated code deletion with validation checks.

Community
Advanced