entropy-scan

Scan codebases for principle violations and generate structured entropy reports.

9|2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/app-vitals/shipwright --skill entropy-scan-app-vitals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: entropy-scan
Source: https://github.com/app-vitals/shipwright/tree/main/plugins/shipwright/skills/entropy-scan
Command: npx skills add https://github.com/app-vitals/shipwright --skill entropy-scan-app-vitals

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill finds principle violations in a codebase and turns them into a structured report, so teams can spot drift early without manual review of every file.

Core Features & Use Cases

  • Repository-wide scanning: Checks local files against defined principles and groups findings by security, dead code, TODO debt, architecture, and documentation gaps.
  • Trend tracking: Can summarize historical scan results to show whether violations are improving or worsening over time.
  • Reporting workflow: Generates an entropy report and appends a quality log entry after a full scan for later comparison and auditing.

Quick Start

Run the entropy-scan skill on the current repository to detect principle violations and write a structured 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 codebase drift and principle violations across my repository?

You can detect codebase drift by scanning local files against defined principles to identify security issues, dead code, TODO debt, architecture flaws, and documentation gaps, producing a structured entropy report.

What is an entropy scan and how does it work for a codebase audit?

An entropy scan inspects local repository files for principle violations across categories like security and architecture, grouping findings into a structured report to help teams spot maintenance drift early.

Can I track whether codebase violations are improving or worsening over time?

Yes, you can track violation trends over time. The scan appends a quality log entry after a full run, allowing you to summarize historical results and compare whether violations are improving or worsening.

What categories of codebase issues does a repository-wide scan cover?

A repository-wide scan covers principle violations grouped into five categories: security, dead code, TODO debt, architecture, and documentation gaps, ensuring comprehensive maintenance auditing.

Do I need any external dependencies to run a codebase audit for principle violations?

No external dependencies are required. The scan relies on local file inspection of skill-defined rules to evaluate the codebase and generate the entropy report without needing additional packages.