OpenParable
Skip to content
← Back to skills

Hard Cut

Development
hard-cut

Hard Cut is an Agent Skill for development published in the udecode/dotai repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Remove a feature completely with no backward compatibility; delete surfaces, callers, tests, docs, fallbacks, stubs, and dead exports.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/udecode/dotai/blob/HEAD/skills/hard-cut/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/hard-cut, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Hard Cut

Use this when a feature should die, not linger.

Rules

  • Delete the surface. Do not deprecate it.
  • Do not leave throw new Error("Not implemented"), placeholder notices, "feature removed" banners, or TODOs about bringing it back unless the user explicitly asks.
  • Do not keep compatibility aliases, deprecated shims, fallback parsing, migration bridges, or dead exports.
  • Delete tests for deleted behavior. Keep tests only for the behavior that still exists.
  • Delete comments that describe deleted code or mourn the old feature.
  • If removal exposes adjacent dead code, keep cutting until the graph is clean.

Sweep

  1. Find the real surface area:
    • exports
    • commands and flags
    • routes
    • UI entrypoints
    • feature flags
    • docs and examples
  2. Trace references with rg.
  3. Delete the implementation and the glue:
    • call sites
    • types
    • state
    • tests
    • docs
    • comments
  4. Grep again for the removed name and obvious aliases.
  5. Run the narrowest honest verification for the surviving product.

Smells

  • deprecated notices
  • not-implemented throws
  • stub handlers
  • dead enum or union members
  • permanently-false feature-flag branches
  • unused env vars and config
  • tests that only prove the deleted feature used to exist

Bias

If the choice is between deleting more code and leaving a zombie surface, delete more code.