hard-cut

Remove a feature's APIs, tests, docs, and references from the codebase.

434|33|Updated Jul 27, 2025
One-click install
npx skills add https://github.com/udecode/kitcn --skill hard-cut
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hard-cut
Source: https://github.com/udecode/kitcn/tree/main/.agents/skills/hard-cut
Command: npx skills add https://github.com/udecode/kitcn --skill hard-cut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove a feature completely with no backward compatibility. Use when a feature should die rather than be deprecated, unshipped, or left as dead code.

Core Features & Use Cases

  • Surface elimination: remove the feature's public APIs, routes, and entry points.
  • Clean sweep of references: delete tests, docs, comments, and stubs that pertain to the removed feature.
  • Integrity assurance: ensure no compatibility aliases or migration bridges remain after removal.

Quick Start

Identify a target feature and remove its surface, tests, docs, and any compatibility shims in a single cohesive sweep.

Frequently Asked Questions about hard-cut

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

FAQPage Schema
How do I remove a feature completely from a codebase without leaving backward compatibility?

Removing a feature completely without backward compatibility requires deleting its public APIs, routes, tests, documentation, and any compatibility aliases in a single cohesive sweep to ensure no dead references remain.

What is the best way to unship a feature and clean up all related code and tests?

Unshipping a feature is best handled by a strict hard-cut workflow that eliminates surface APIs, removes associated code and tests, purges documentation and comments, and verifies no dead aliases or references remain.

When should I hard cut a feature instead of deprecating it?

Hard cut a feature instead of deprecating it when stakeholders demand the feature die immediately rather than be unshipped gradually or left as dead code with migration bridges and backward compatibility shims.

How do I ensure no dead aliases or migration bridges remain after feature removal?

Ensuring no dead aliases or migration bridges remain after feature removal requires an integrity assurance step that verifies all public APIs, routes, stubs, and references have been purged from the codebase.

Does feature removal require deleting documentation and comments too?

Feature removal requires deleting documentation and comments to achieve a clean sweep of references, ensuring no stubs, tests, or surface APIs pertaining to the removed feature are left behind in the repository.