skills.rest
autopus-ai
autopus-aiOFFICIAL
Explore all skills by this author →
GitHub

entropy-scan

Measures codebase entropy and detects technical debt hotspots using complexity and churn metrics.

111|73|Updated Mar 20, 2026
Search Tags:#code quality#refactoring#go#technical debt#cyclomatic complexity#entropy#hotspot analysis
One-click install
npx skills add https://github.com/autopus-ai/autopus-adk --skill entropy-scan-autopus-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: entropy-scan
Source: https://github.com/autopus-ai/autopus-adk/tree/main/.omp/skills/entropy-scan
Command: npx skills add https://github.com/autopus-ai/autopus-adk --skill entropy-scan-autopus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate disorder over time, making it hard to know which files need refactoring first. This Skill quantifies technical debt by measuring cyclomatic complexity, coupling, duplication, and file size, then ranks files by an entropy score so teams know exactly where to focus cleanup efforts. ## Core Features & Use Cases - Complexity Measurement: Evaluates cyclomatic complexity with defined thresholds (1-5 simple, 16+ requires immediate refactoring) using tools like gocyclo. - Hotspot Detection: Combines git change frequency with complexity scores to identify the riskiest files in the repository. - Prioritized Remediation: Calculates a priority score (change frequency × complexity × coupling) and classifies issues into P1, P2, and P3 tiers with a structured Markdown report. - Use Case: Before a sprint planning meeting, run an entropy scan on a Go service to produce a table of the top 5 hotspot files with recommended actions, giving the team a data-driven refactoring backlog. ## Quick Start Ask the agent to run an entropy scan on this repository and report the top hotspot files with refactoring priorities.

Frequently Asked Questions about entropy-scan

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

FAQPage Schema
How do I measure cyclomatic complexity in a Go codebase?▼

Use gocyclo with a threshold flag such as 'gocyclo -over 10 ./...' to list functions exceeding a complexity of 10. Functions scoring 11-15 should be flagged for review, and those above 16 should be refactored immediately.

How to find code hotspots using git history?▼

Combine git log change frequency with complexity scores to find hotspots. Run git log over the last three months, count file change occurrences, and multiply by each file's complexity to rank the riskiest files.

What metrics indicate high technical debt in a repository?▼

Key indicators are cyclomatic complexity above 10, files over 500 lines, logic duplicated three or more times, and circular import dependencies. The entropy score multiplies change frequency, complexity, and coupling to prioritize fixes.

Does this entropy scan work with languages other than Go?▼

The documented commands target Go specifically, using gocyclo, go list, and Go function parsing. The underlying thresholds and hotspot methodology are language-agnostic, but you would need equivalent tooling for other languages.

When should a file be split based on file size?▼

Files under 200 lines are considered normal, 200-500 lines need attention, and 500-1000 lines should be split. Files exceeding 1000 lines require immediate decomposition into smaller modules.

Related Skills

Explore More Software Engineering Skills→
extremecoder-rgbextremecoder-rgb

git-forensics

Analyze git history to detect hotspots, churn, and bus-factor risk.

Community
Advanced
howellshowells
2

heathen

Rank god-file candidates and detect duplicated code blocks in JavaScript and TypeScript repositories.

Community
Advanced
statick88statick88
1

security-auditor

Scan codebases for security vulnerabilities, dependency issues, and secret exposure.

Community
Advanced
koderoverkoderover
7

sonar

Retrieve and analyze SonarQube code quality metrics and quality gate statuses.

Official
Intermediate