entropy-scan

Detect codebase drift and inconsistencies with P0/P1/P2 priorities.

Updated Aug 23, 2026

Search Tags:#refactor #code-quality #drift-detection #static-analysis #report #entropy

Ready to run

npx skills add https://github.com/mojwang/macbook-dev-setup --skill entropy-scan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: entropy-scan
Source: https://github.com/mojwang/macbook-dev-setup/tree/main/config/skills/entropy-scan
Command: npx skills add https://github.com/mojwang/macbook-dev-setup --skill entropy-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Detect drift, inconsistencies, and accumulating technical debt before they compound across a codebase, by orchestrating automated scans and interpreting results.

Core Features & Use Cases

Scan hardcoded colors to identify token color usages across components.
Detect stale file references and broken import paths to prevent runtime errors.
Find unused exports to minimize dead code and simplify maintenance.
Model-driven checks that surface patterns and group related issues for actionable remediation.
Produce an Entropy Report that consolidates findings with file:line references for quick fixes.

Quick Start

Run entropy-scan to collect scan data, interpret findings, and produce the entropy report.

Frequently Asked Questions about entropy-scan

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

FAQPage Schema

How do I detect technical debt and codebase drift before it compounds?▼

To detect technical debt and codebase drift, run an automated static analysis scan that identifies hardcoded colors, stale file references, and unused exports, then interprets findings with P0/P1/P2 priorities to guide remediation.

What is the best way to find unused exports and stale references in my codebase?▼

The best way to find unused exports and stale references is to run an entropy scan that uses model-driven checks to group related issues, producing a structured report with exact file:line references for quick and actionable fixes.

How do I generate a structured report for codebase inconsistencies and technical debt?▼

Generating a structured technical debt report requires running an entropy scan that collects data on hardcoded colors and broken import paths, interprets the results by priority, and outputs an Entropy Report with file:line references for quick fixes.

Can I use static analysis to identify hardcoded colors across my components?▼

Yes, you can use static analysis to scan for hardcoded colors and token color usages across components, helping you surface inconsistencies and standardize your design system before runtime errors or visual drift occur.

Do I need any dependencies or external libraries to run an entropy scan for technical debt?▼

No, you do not need any external dependencies to run this entropy scan; it coordinates an internal scripts directory with model-driven checks to produce a structured technical debt report without requiring additional library installations.