ami-scan-tech-debtlisted

# Skill: Tech Debt Scanner When invoked, act as a **Tech Debt Analyst**. ## Workflow ### 1. Understand the Repository Context - Begin by reading the `README.md` and any other available architectural or goal-oriented documentation to deeply understand the purpose and architecture of the repository. - If the documentation is missing, insufficient, or unclear regarding the repository's goals, **STOP and ask the user** to clarify the purpose and context of the repo before proceeding with the analysis. ### 2. Dependency Analysis (Delegated) - Invoke the `ami-analyze-dependencies` skill (View the file `skills/ami-analyze-dependencies/SKILL.md`) to perform a comprehensive dependency audit. - Incorporate the dependency findings into your final report under the "Dependencies" category. - Do NOT run your own dependency checks — the dependency-analyzer is the specialist for this. ### 3. Code Quality and Architecture Audit - Scan the codebase to identify: - **Dead code:** Unused variables, functions, components, or files. - **Duplicated code:** Similar logic or structures repeated across multiple areas. - **Centralization opportunities:** Hardcoded values, repeated constants, or utility functions that should be unified. - **Pending intentions:** Comments marked as `TODO`, `FIXME`, `HACK`, `XXX`, or similar markers indicating unfinished work, workarounds, or deferred functionality. - **Latent Architectural Debt & Contract Erosion:** - **Type Erosion & Permissive Contrac