Menú
Deprecate and remove code safely. Use when replacing systems, removing unused features, or consolidating duplicate implementations.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Create and update AGENTS.md project rules. Use when authoring or amending the cross-tool conventions agents must follow.
Write forward-looking startup instructions for the next session, then reset context to save costs. Use when the context is getting long or before switching focus.
Run pre-release checks, pick the version bump, and cut the release. Use when ready to tag and release.
Create and maintain a specification that states what to build, not how. Use when writing a spec, editing requirements, or defining acceptance criteria.
Run all review dimensions against a diff or a path. Use when reviewing a feature branch before merge, reviewing someone else's PR, or auditing a file path.
Create or update project documentation. Use when creating architecture docs, runtime docs, reference docs, or design documents that explain what the system does.
| name | deprecation |
| description | Deprecate and remove code safely. Use when replacing systems, removing unused features, or consolidating duplicate implementations. |
Code is a liability, not an asset. Every line requires maintenance — bug fixes, dependency updates, security patches, cognitive overhead. When equivalent functionality requires less code or better abstraction, the old version should be retired.
Value comes from functionality, not code volume. Less code serving the same purpose is strictly better.
All observable behaviors become dependencies. Users rely on bugs and undocumented side effects. Deprecation requires active migration, not just announcement.
Don't maintain two systems in parallel. Land the replacement, migrate consumers, remove the old system. Dual systems double maintenance cost.
If you own the infrastructure being deprecated, you are responsible for migrating your users — or providing backward-compatible updates that require no migration.
Code with no owner but active dependents. Signs:
Either assign an owner and maintain it, or deprecate it with a migration plan. Zombie code cannot remain suspended.
