code-feature-remover

Remove Compose feature code with bottom-up dependency-aware deletion.

2|Updated May 12, 2026
One-click install
npx skills add https://github.com/youfengknight/Android-Code-Skills --skill code-feature-remover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-feature-remover
Source: https://github.com/youfengknight/Android-Code-Skills/tree/main/code-feature-remover
Command: npx skills add https://github.com/youfengknight/Android-Code-Skills --skill code-feature-remover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you safely delete a feature from a Kotlin/Jetpack Compose codebase by ensuring you remove all dependent UI, state, event logic, helper functions, imports, and related resources without leaving broken references or dead code.

Core Features & Use Cases

  • Dependency-aware deletion workflow: Builds a “function dependency tree” so you can identify what must be removed together (state, UI components, event handlers, helper functions, imports, and resources).
  • Bottom-up removal order: Recommends deleting from leaf nodes to root (UI → events → state → helpers → imports → resources) to minimize compile errors during refactors.
  • Post-change verification checklist: Guides you to confirm compilation, remove unused imports/variables, and validate feature behavior via app/test runs.
  • Use Case: When a product requirement changes (e.g., removing a search feature or a toggle-based UI path), use this Skill to delete the feature end-to-end while keeping the rest of the screen stable.

Quick Start

Ask the AI to generate a deletion checklist and step-by-step code changes to remove the specified Compose feature, including UI/state/event/utility cleanup, unused import/resource removal, and the exact verification steps to confirm the project compiles and behaves correctly.

Frequently Asked Questions about code-feature-remover

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

FAQPage Schema
How do I safely remove a feature from a Jetpack Compose codebase?

Safely removing a feature from a Jetpack Compose codebase requires analyzing function dependencies and applying a bottom-up deletion order across UI, events, state, helpers, imports, and resources to prevent broken references.

What is the safest order for deleting Compose UI components and state?

The safest order for deleting Compose UI components and state is a bottom-up workflow: delete leaf nodes first, moving from UI to events, then state, helpers, imports, and finally resources to minimize compile errors.

How do I eliminate dangling references when refactoring feature code?

To eliminate dangling references when refactoring feature code, identify all dependent event handlers, helper functions, and imports together, remove them in a bottom-up order, and run unused-symbol validation to catch dead code.

Can I use this dependency analysis approach for removing conditional rendering paths?

Yes, you can use this dependency analysis approach for removing conditional rendering paths, as it identifies related callbacks and state variables to ensure complete feature removal while keeping the rest of the screen stable.

What should I verify after completing a code cleanup for feature removal?

After completing a code cleanup for feature removal, you should verify project compilation, confirm the removal of unused imports and variables, and validate the app's behavior through test runs to ensure no dead code remains.