dark-code-audit

Identify dark-code risks and generate a structured comprehension audit report.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/az9713/dark-code-skills --skill dark-code-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dark-code-audit
Source: https://github.com/az9713/dark-code-skills/tree/main/skills/dark-code-audit
Command: npx skills add https://github.com/az9713/dark-code-skills --skill dark-code-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Dark Code Audit helps teams identify and measure comprehension gaps in codebases where AI-generated changes shipped without clear understanding. It surfaces hotspots, ownership gaps, and documentation deficits to prevent blind trust in automated velocity.

Core Features & Use Cases

  • Auto-discovery of modules and context layers (MODULE_MANIFEST.md, BEHAVIORAL_CONTRACTS.md, DECISION_LOG.md)
  • Structured hotspot map, ownership gap analysis, and a formal comprehension debt scorecard
  • Guided interview approach and step-by-step analysis to prepare governance-ready audit reports
  • Produce audit reports tailored for security reviews, compliance checks, or major refactors

Quick Start

Run the audit from the repository root to generate a full comprehension audit report.

Frequently Asked Questions about dark-code-audit

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

FAQPage Schema
How do I audit AI-generated code for comprehension debt and ownership gaps?

To audit comprehension debt, run a structured analysis from your repository root to auto-discover modules, map hotspots, and generate a formal report documenting ownership gaps and missing context layers.

What is dark code in a software project and how do I identify it?

Dark code refers to AI-generated changes shipped without clear understanding or documentation, which you identify by producing a structured comprehension audit that surfaces missing context layers and behavioral contracts.

How do I generate MODULE_MANIFEST.md and BEHAVIORAL_CONTRACTS.md for a codebase?

You generate MODULE_MANIFEST.md and BEHAVIORAL_CONTRACTS.md artifacts by running an automated audit process that auto-discovers modules and creates context layers to document existing code behavior and structure.

Can I use a comprehension audit for security reviews and post-incident investigations?

Yes, a comprehension audit is specifically tailored for security reviews, compliance checks, architecture decisions, and post-incident investigations by producing governance-ready reports with a formal debt scorecard.

What's the best way to document codebase risks before a major refactor?

The best way to document risks before a major refactor is conducting a guided interview analysis that produces a structured hotspot map, ownership gap analysis, and a formal comprehension debt scorecard.

Does a dark code audit work on multi-team modules with absent context layers?

Yes, this audit specifically applies to codebases with multi-team modules and absent context layers, generating DECISION_LOG.md files and documenting ownership gaps to prevent blind trust in automated velocity.