tech-debt-finder

Scan Python projects for technical debt and create prioritized GitHub issues.

4|Updated Jan 1, 2026
One-click install
npx skills add https://github.com/vertexcover-io/tarash --skill tech-debt-finder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt-finder
Source: https://github.com/vertexcover-io/tarash/tree/main/.claude/skills/tech-debt-finder
Command: npx skills add https://github.com/vertexcover-io/tarash --skill tech-debt-finder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans codebases to identify architectural and code-level technical debt, producing a prioritized report and creating a GitHub issue with actionable findings.

Core Features & Use Cases

  • Dependency & Environment scan to surface known CVEs, outdated and unused dependencies, and pinning gaps
  • Structural & Code pattern analysis to detect god modules, deep nesting, and complexity hotspots
  • Code-pattern discovery for common anti-patterns and duplication hints with actionable remediation steps
  • Use Case: Run the scan on a large mono-repo to generate a structured debt report and automatically open an issue with prioritized fixes

Quick Start

Run tech-debt-finder on your repository to generate a prioritized report and automatically create a GitHub issue with actionable findings.

Frequently Asked Questions about tech-debt-finder

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

FAQPage Schema
How do I find and triage technical debt in a large Python codebase?

You can identify technical debt by scanning your Python project for architectural issues like god modules, deep nesting, and dependency vulnerabilities. The tool produces a prioritized report highlighting complexity hotspots and actionable remediation steps.

Can I automatically create GitHub issues for code quality findings and static analysis results?

Yes, you can automatically create a GitHub issue containing a structured, prioritized report of your code quality findings. This automated issue creation workflow directly surfaces static analysis results and actionable technical debt remediation steps to your development team.

Does static analysis for technical debt scan project dependencies and environments for security risks?

Yes, static analysis for technical debt includes a dependency and environment scan that surfaces known CVEs, outdated packages, and unused dependencies. This risk management check identifies pinning gaps and security vulnerabilities across your project's environment.

What is the best way to detect code anti-patterns and duplication hints across multiple packages?

The best way to detect code anti-patterns and duplication hints across multiple packages is by running a structural and code pattern analysis. This process discovers common anti-patterns and duplication hotspots, providing a structured report with specific remediation steps.

Can I use tech debt scanning on a large monorepo with multiple test configurations?

Yes, technical debt scanning is designed for large codebases with multiple packages, dependencies, and test configurations. You can run the scan from the repository root to comprehensively analyze the entire monorepo and generate a consolidated debt report.