zero-tech-debt

Solid

Rework a patch from its intended end-state, not from the historical path that produced it — delete compat cruft, mode flags, fallbacks, and wrappers no one calls anymore. Triggers "zero tech debt", "rewrite as if from scratch", "delete the compat layer", "kill the legacy path", "this has too many flags", or when a feature has accreted mode props and shims over multiple iterations and you want the shape it should have shipped with.

AI & Automation 42 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
54
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Zero Tech Debt Rework the change from the intended end-state, not from the historical path that produced the current patch. The principles (no compat hacks, no abstractions you don't need, no dead branches) are in `AGENTS.md` — this skill is the workflow for applying them to a specific patch. ## When to invoke - A feature has accreted mode props, route aliases, or fallbacks across iterations - A migration left behind a compatibility shim that no current caller uses - You catch yourself preserving an old shape "just in case" with no concrete caller in mind - The diff is bigger than the change it represents because it's making the old structure better instead of removing it For restructuring code outside the current diff use `/refactor`. This skill is for the patch in front of you. (Claude Code 2.1.147 renamed `/simplify` to `/code-review` and removed the old cleanup-and-fix behavior; the native command is now a correctness reporter, not a code tightener.) ## Steps 1. **State the intended end-state.** One or two sentences. If you can't name it, stop and ask the user — you'll otherwise optimize toward the current shape. 2. **Search for real callers before preserving compatibility.** For each mode prop, route alias, fallback branch, or wrapper: grep for current callers. No caller → delete it, don't improve it. 3. **Reshape around the final product surface.** Prefer one clear component or flow over mode flags. Split only when there's an obvious boundary — state, layout, co...

Details

Author
darkroomengineering
Repository
darkroomengineering/cc-settings
Created
7 months ago
Last Updated
today
Language
TypeScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

zero-tech-debt

Rework a change as if the intended UX and architecture had existed from day one — deleting compatibility cruft, dead branches, and accidental complexity instead of patching around them. Use when refactoring, cleaning up after a feature lands, removing flags, collapsing legacy paths, or when the user says the code "should look like X from scratch".

12 Updated today
susomejias
Code & Development Solid

refactor

Behavior-preserving restructuring of code that is NOT in your current diff — extract modules, rename across files, untangle abstractions, pay down tech debt. For tightening just-changed code use `/zero-tech-debt` instead. Triggers "refactor X", "reorganize this module", "restructure", "extract Y from Z", "pay down tech debt".

42 Updated today
darkroomengineering
AI & Automation Listed

refactor-skills

Reviews the markdown and template files changed in the current session and tightens them for agent performance — sharper trigger descriptions, progressive disclosure, imperative voice, one-claim-per-bullet, fewer redundant rules — while preserving every workflow step, constraint, and trigger condition. Use when the user has just edited one or more skill or prompt files (`SKILL.md`, `references/*.md`, `recipes/*.md`, agent templates, slash-command prompts) and wants a tightening pass before committing, or invokes "/refactor-skills", "refactor this skill", "tighten the skill", "polish SKILL.md", "make this skill leaner". Behaviour-preserving only — never use this to add features, expand scope, or remove rules.

0 Updated 1 weeks ago
usrrname