skills.rest
krishna-cyber
krishna-cyberCOMMUNITY
Explore all skills by this author →
GitHub

hard-cut

Identifies and removes entire features from a codebase using regex-based dependency tracing and deletion rules defined in .mcu files.

Updated Jul 2, 2026
Search Tags:#code refactoring#code cleanup#feature removal#technical debt reduction#legacy code management
One-click install
npx skills add https://github.com/krishna-cyber/plate_js_rich_text_editor --skill hard-cut-krishna-cyber
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hard-cut
Source: https://github.com/krishna-cyber/plate_js_rich_text_editor/tree/main/.agents/skills/hard-cut
Command: npx skills add https://github.com/krishna-cyber/plate_js_rich_text_editor --skill hard-cut-krishna-cyber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The hard-cut skill provides a comprehensive and aggressive approach to remove entire features from a codebase, including surface implementations, dependencies, and related resources.

Core Features & Use Cases

  • Complete Removal: Deletes the surface area, including commands, routes, UI elements, and tests related to the feature being cut.
  • Automated Cleaning: Traces through all references and cleans up related code and comments to maintain a clean and functional codebase.
  • Use Case: Ideal for when you want to remove a feature that is no longer needed, avoiding technical debt and maintaining a healthy codebase.

Quick Start

Activate the hard-cut skill by entering "Perform hard-cut on feature X".

Frequently Asked Questions about hard-cut

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

FAQPage Schema
How do I safely remove entire features from a legacy codebase?▼

To remove entire features from a legacy codebase, you need an automated approach that traces dependencies and deletes surface implementations, commands, routes, and related tests to eliminate technical debt.

What is the best way to clean up unneeded code components and technical debt?▼

The best way to clean up unneeded code components is utilizing regex tracing to identify all related dependencies and surface area, ensuring complete deletion of routes, UI elements, and associated tests.

How do I define removal criteria for automated code refactoring?▼

To define removal criteria for automated code refactoring, you must create .mdc rule files that specify the targeted feature boundaries for the deletion process.

Can I use automated feature removal to eliminate routes and UI elements?▼

Yes, automated feature removal can eliminate routes and UI elements by tracing through all references and cleaning up related code, comments, and dependencies to maintain a functional codebase.

Does complete feature deletion require manually tracing code dependencies?▼

No, complete feature deletion does not require manual tracing because the process utilizes regex to automatically trace code dependencies and clean up all related references.

When should I not use aggressive feature removal on my codebase?▼

You should avoid aggressive feature removal when your codebase lacks clear .mdc rule files to define removal criteria, as incorrect boundaries may break complex legacy systems.

Related Skills

Explore More Software Engineering Skills→
mymx2mymx2
4

deprecation-and-migration

Plan deprecation and migration of legacy systems with zero active usage verification.

Community
Advanced
imMamdouhaboammarimMamdouhaboammar

reducing-entropy

Evaluate refactoring changes for net decreases in code volume.

Community
Intermediate
smileynetsmileynet

code-pruning

Detect and remove dead code, unused dependencies, and codebase bloat.

Community
Intermediate
duynhneduynhne

refactoring-expert

Identify and remediate code smells using refactoring techniques without altering external behavior.

Community
Advanced