SkillsAdd

jorgealves/agent_skills

technical-debt-visualizer

Generates a heat-map and metrics report of a repository based on code complexity, lack of tests, and 'TODO/FIXME' density. Use when you need to identify high-risk areas for refactoring or when planning technical debt reduction sprints.

First seen Jan 30, 2026

Installation

$ npx skills add jorgealves/agent_skills --skill technical-debt-visualizer
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-aigateway Shared topics
microsoft/azure-skills

Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…

566.3K installs
azure-compute Shared topics
microsoft/azure-skills

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…

510K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-cli Shared topics
prisma/skills

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, …

267K installs
supabase Shared topics
supabase/agent-skills

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge F…

263K installs

Also in this package

Other skills from jorgealves/agent_skills · top by installs.

npx skills add jorgealves/agent_skills
gdpr-ccpa-privacy-auditor 393 python-security-scanner 309 prompt-injection-scanner 262 pii-sanitizer 251 documentation-generator 250 python-data-pipeline-designer 250 hipaa-compliance-guard 233 license-compliance-auditor 229 secret-leak-detector 221 agent-capability-discovery 220

Browse all from jorgealves/agent_skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License license-compliance-auditor
Default branch main
Open issues 1
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,894 B
  • docs SUMMARY.md 268 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 165 installs

SKILL.md

Technical Debt Visualizer

Purpose and Intent

The technical-debt-visualizer provides a data-driven view of software quality. It helps engineering leaders and developers prioritize refactoring work by identifying files that are both complex and frequently changed—the "high-interest" technical debt.

When to Use

  • Sprint Planning: Run this before a dedicated refactoring sprint to identify the best "ROI" targets.
  • Architectural Reviews: Use to visualize the impact of legacy systems on the overall codebase health.
  • Due Diligence: Quickly assess the health of a new or acquired repository.

When NOT to Use

  • Performance Benchmarking: This tool measures code structure and maintainability, not runtime performance.
  • Absolute Complexity Rating: Metrics like cyclomatic complexity are indicators, not absolute rules; some complex logic is unavoidable.

Input and Output Examples

Input

source_path: "./src"
output_format: "markdown"

Output

A markdown report highlighting "Hotspots"—files that have high complexity and low test coverage.

Error Conditions and Edge Cases

  • No Git History: If run on a non-git directory, the "change frequency" metric will be unavailable.
  • Unsupported Languages: Complexity analysis is language-dependent; unknown extensions will be reported with a lower confidence score.

Security and Data-Handling Considerations

  • Local Scan: The analysis is performed entirely in memory on the local machine.
  • No Execution: The tool uses static analysis; it never runs the code it is analyzing.