zero-tech-debt

Refactor codebases to align with end-state architecture and remove dead code.

9|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/susomejias/rembric --skill zero-tech-debt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zero-tech-debt
Source: https://github.com/susomejias/rembric/tree/main/.agents/skills/zero-tech-debt
Command: npx skills add https://github.com/susomejias/rembric --skill zero-tech-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of accumulating unnecessary technical debt from incremental patches, legacy compatibility code, dead branches, and accidental complexity that bloats codebases, reduces maintainability, and slows down future development.

Core Features & Use Cases

  • End-State Refactoring: Reshapes code changes to match the intended final product architecture and user experience instead of making minimal diffs from existing messy code.
  • Automated Cruft Removal: Identifies and deletes unused compatibility paths, dead code branches, redundant feature flags, and legacy route aliases with no active callers.
  • Use Case: After landing a new feature, use this Skill to clean up temporary workarounds, unused mode flags, and duplicated permission rules so the codebase aligns with the original product design.

Quick Start

Use the zero-tech-debt skill to refactor the new project sharing flow to remove all temporary guest access compatibility code and unused fallback permission checks.

Frequently Asked Questions about zero-tech-debt

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

FAQPage Schema
How do I refactor legacy code to match the intended product architecture instead of patching?

Legacy code refactoring reshapes changes to align with the intended end-state architecture and user experience, replacing incremental historical patches with a clean product design. This approach removes accidental complexity and ensures the codebase matches original design goals.

What is the best way to remove dead code branches and unused feature flags?

Dead code removal identifies and deletes unused compatibility paths, redundant feature flags, and legacy route aliases. The process verifies that removed code paths have no active callers prior to deletion, ensuring safe elimination of unused branches and duplicated rules.

When do I need to clean up technical debt after landing a new feature?

Technical debt cleanup is needed after landing a feature to eliminate temporary workarounds, unused mode flags, and duplicated permission checks. Post-feature cleanup consolidates business rules into single sources of truth, aligning the codebase with the original product design.

Can I consolidate duplicated business rules into a single source of truth during refactoring?

Consolidating duplicated business rules into a single source of truth is a core function of end-state refactoring. It collapses legacy code paths and accidental complexity, verifying removed code paths have no active callers prior to deletion for safe rule consolidation.

Does end-state refactoring work for removing temporary guest access compatibility code?

End-state refactoring works for removing temporary guest access compatibility code and unused fallback permission checks. It reshapes code changes to match the final product architecture, safely deleting unused compatibility paths and dead branches with no active callers.