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.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "technical-debt-visualizer" with this command: npx skills add jorgealves/agent_skills/jorgealves-agent-skills-technical-debt-visualizer

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.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHubOpen in ClawHub

Related Skills

Related by shared tags or category signals.

Coding

python-data-pipeline-designer

No summary provided by upstream source.

Repository SourceNeeds Review
67-jorgealves
Coding

python-formatter-advisor

No summary provided by upstream source.

Repository SourceNeeds Review
58-jorgealves
Coding

python-dependency-resolver

No summary provided by upstream source.

Repository SourceNeeds Review
58-jorgealves
Coding

python-venv-manager

No summary provided by upstream source.

Repository SourceNeeds Review
58-jorgealves