skills.rest
autorundev
autorundevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

system-integrity-audit

Inspect codebases for dead code, broken wiring, and orphaned components by severity.

1|Updated Apr 14, 2026
Search Tags:#codebase analysis#system integrity#code health#software audit#dead code detection
One-click install
npx skills add https://github.com/autorundev/autorun-skills --skill system-integrity-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: system-integrity-audit
Source: https://github.com/autorundev/autorun-skills/tree/main/system-integrity-audit
Command: npx skills add https://github.com/autorundev/autorun-skills --skill system-integrity-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of identifying and resolving dead code, broken wiring, orphaned components, unused DB tables, and other issues in complex software systems.

Core Features & Use Cases

  • System Inventory: Builds a complete inventory of all definitions and configurations in the codebase.
  • Wiring Trace: Verifies that all components are connected and reachable.
  • Dead Code Detection: Identifies and classifies dead code, including functions, methods, classes, constants, and more.
  • Use Case: Conduct a system integrity audit after a major refactoring or before a release to ensure the system is robust and free of unused or broken components.

Quick Start

Run the system-integrity-audit skill to begin the deep system integrity check on your codebase.

Frequently Asked Questions about system-integrity-audit

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

FAQPage Schema
How do I detect dead code and unused resources in a complex codebase?▼

A system integrity audit detects dead code by building a complete inventory of all definitions and configurations, tracing wiring to verify reachability, and classifying unused functions, methods, classes, and constants by severity.

When do I need to perform a software audit for system integrity?▼

You should perform a software audit for system integrity after a major refactoring or before a release. It ensures complex, mature projects remain robust by identifying orphaned components, broken wiring, and unused database tables.

How do I check if all components are wired and reachable in my project?▼

To check if components are wired and reachable, an audit performs a wiring trace that verifies all connections across the codebase. This process identifies orphaned components and broken links.

What is the best way to find orphaned components and unused DB tables?▼

The best way to find orphaned components and unused DB tables is a comprehensive system integrity check. It inventories all configurations, traces reachability, and flags unused resources classified by severity.

Is a system integrity audit suitable for small or early-stage projects?▼

A system integrity audit is designed for complex, mature projects. It requires extensive analysis to verify wiring and identify dead code, making it less suitable for early-stage or small codebases.

Related Skills

Explore More Software Engineering Skills→
stribusstribus
1

reversa-scout

Identify folders, languages, frameworks, dependencies, and entry points in legacy codebases.

Community
Advanced
artivillaartivilla

knip

Detect unused files, dependencies, and exports in JavaScript/TypeScript projects.

Community
Advanced
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate
HafizFasihHafizFasih

monitor-system

Monitor system health across watchers and MCP servers with automatic recovery.

Community
Advanced