dark-code-audit

Diagnose dark code accumulation in AI-generated codebases and produce a prioritized risk assessment.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill dark-code-audit-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dark-code-audit
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/prompt-workflows/skills/dark-code-audit
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill dark-code-audit-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams shipping large volumes of AI-generated code accumulate "dark code" — code no human ever understood — creating hidden systemic risk that surfaces during incidents, security reviews, or regulatory scrutiny. This Skill diagnoses where that risk concentrates before remediation begins. ## Core Features & Use Cases - Structured Context Gathering: Interviews the user in four staged groups covering system architecture, AI tool usage, team ownership, and deployment practices. - Two-Dimensional Risk Analysis: Classifies hotspots as structural dark code (emergent agent-assembled behavior) or velocity dark code (authored code nobody comprehended), plus compounding factors like ownership gaps and talent erosion. - Prioritized Risk Report: Produces a hotspot severity map, top-3 failure scenarios, ownership gap list, comprehension debt scorecard, and an ordered action plan. - Use Case: Before a security review or board-level risk assessment, run the audit quarterly to identify which services have critical comprehension gaps and which remediation actions deliver the highest impact. ## Quick Start Use the dark-code-audit skill to assess where dark code is accumulating in our system and prioritize what to fix first.

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 risk?

Run a dark code audit that gathers context on your architecture, AI tool usage, team ownership, and deployment process, then maps hotspots by severity. The output is a prioritized risk assessment with concrete failure scenarios and an action plan.

What is dark code in software engineering?

Dark code is code that was never understood by any human at any point in its lifecycle. It comes in two forms: structural dark code from emergent agent-assembled behavior, and velocity dark code from AI-authored code that passed checks without human comprehension.

When should I run a dark code audit?

Run it before starting remediation work, quarterly as a standing practice, or after periods of high-velocity AI-assisted development. It is also useful before security reviews, regulatory preparation, or board-level risk assessments.

What information does a dark code audit require?

The audit asks about four areas: system architecture and data flows, which AI coding tools are used and at what volume, team structure and ownership mapping, and the review and deployment process including recent incidents.

What are the limitations of a dark code audit?

The audit only assesses based on information the user provides and flags areas with insufficient data rather than guessing. Findings that require hands-on codebase investigation are explicitly distinguished from what can be identified from descriptions alone.