find-tech-debt-ai-kit

Name: find-tech-debt-ai-kit
Availability: InStock
Author: ducthang-hub

Scan repositories for coding standard violations and generate Jira-ready remediation tasks.

Updated May 11, 2026

Search Tags:#code quality #static analysis #coding standards #tech debt #repository audit #merge conflict avoidance #jira tasks

Ready to run

npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill find-tech-debt-ai-kit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: find-tech-debt-ai-kit
Source: https://github.com/ducthang-hub/nw-ai-kit/tree/main/.agents/skills/find-tech-debt-ai-kit
Command: npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill find-tech-debt-ai-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams quickly uncover recurring coding standard violations and convert them into practical remediation work that developers can tackle without stepping on each other’s changes.

Core Features & Use Cases

Tech-debt discovery: Scans a repository by reading skill rules and searching for concrete and conceptual violations.
Actionable, merge-conflict-safe planning: Groups fixes by file or area so each Jira card targets a distinct scope.
Jira-ready remediation artifacts: Produces a prioritized top-5 summary and detailed task descriptions with acceptance criteria.

Quick Start

Use the find-tech-debt-ai-kit skill to analyze your repository and generate the top 5 widespread coding standard violations as Jira-ready tasks grouped by file or area.

Frequently Asked Questions about find-tech-debt-ai-kit

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

FAQPage Schema

How do I audit code quality and generate Jira tasks for standard violations?▼

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.

How does a repository audit locate exact lines of bad coding patterns?▼

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.

Can I group code cleanup tasks by file to avoid merge conflicts?▼

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.

Do I need SKILL.md files to scan for coding standard violations?▼

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.

What is the best way to prepare merge-conflict-free remediation work for developers?▼

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.