dark-code-audit

Interview architecture, AI tool usage, ownership, and deployment to assess dark-code risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and assesses dark-code risks, which are code or runtime behaviors that remain unexplained by any human, helping prevent systemic risks and improving code comprehension.

Core Features & Use Cases

  • System Architecture Assessment: Gathers and analyzes information about system architecture.
  • AI Tool Usage Evaluation: Evaluates the team's usage of AI coding tools and practices.
  • Ownership and Development Analysis: Assesses team ownership structure, code development processes, and deployment practices.
  • Risk Assessment: Produces a detailed risk assessment report.

Quick Start

Initiate a dark-code audit to evaluate structural and velocity risks.

Frequently Asked Questions about dark-code-audit

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

FAQPage Schema
What is dark code and how do I assess its risk in my system architecture?

Dark code refers to code or runtime behaviors unexplained by any human. You assess dark-code risk by interviewing system architecture, AI tool usage, ownership, and deployment practices to identify structural and velocity hazards.

How do I audit code generated by AI tools for systemic risk?

To audit AI code evaluation risks, you evaluate the team's AI coding tool usage and practices. This AI code evaluation assesses comprehension debt and ownership gaps to produce a targeted risk assessment report.

What's the best way to identify ownership gaps and comprehension debt in code development?

The best way to identify ownership gaps is through an ownership and development analysis. It assesses team ownership structure and code development processes, outputting a comprehension debt scorecard to highlight unexplained behaviors.

Can I generate a hotspot map for runtime behaviors that remain unexplained by any human?

Yes, you can generate a hotspot map by assessing structural and velocity dark-code risks. The audit outputs a risk assessment report that includes a hotspot map detailing these unexplained runtime behaviors.

Does an AI code evaluation require specific deployment practices to assess velocity risks?

AI code evaluation requires analyzing your deployment practices to accurately assess velocity dark-code risks. It evaluates how team development processes and deployment workflows contribute to systemic unexplained behaviors.