ami-tech-debt-scannerlisted

Follow these instructions to scan a repository for technical debt: 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:** - Inspect the package management files (e.g., `package.json`, `requirements.txt`, etc.). - Identify libraries and dependencies that appear to be significantly outdated, unmaintained, or deprecated. 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. - **Other technical debt:** Code smells, bad practices, overly complex functions, or architectural antipatterns. 4. **Classify and Report Findings:** - If no technical debt is found during your audit, you MUST simply output **"NO TECH DEBT FOUND"**. Do not list anything, and do not proceed to step 5. - If technical debt is found, compile all findings into a structured list. - For EACH findi