find-tech-debt-ai-kit

You can audit code quality by scanning the repository with grep and semantic search to find widespread coding standard violations. It extracts actionable rules from SKILL.md files and outputs a prioritized top-5 summary grouped by file or area.

A repository audit locates bad patterns by searching for concrete and conceptual violations across the codebase. It identifies every coding standard violation with exact line numbers and clickable references for quick remediation.

Yes, you can group code cleanup tasks by file or area. This merge-conflict-safe planning ensures each Jira card targets a distinct scope, allowing developers to execute remediation work in parallel without stepping on each other’s changes.

Yes, you need SKILL.md files to scan for coding standard violations. The audit requires extracting actionable rules from these files to locate concrete and conceptual violations and generate prioritized remediation work.

The best way to prepare remediation work is to group fixes by file or area so each task targets a distinct scope. This generates Jira-ready artifacts with acceptance criteria, enabling parallel developer execution without merge conflicts.