codebase-audit

Parse SKILL.md YAML frontmatter and enumerate valid Skill Units.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dylan-conlin/orch-go --skill codebase-audit-dylan-conlin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-audit
Source: https://github.com/dylan-conlin/orch-go/tree/main/skills/src/worker/codebase-audit
Command: npx skills add https://github.com/dylan-conlin/orch-go --skill codebase-audit-dylan-conlin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires worker-base.

What problem does it solve?

Systematic, dimensioned audits of codebases to surface actionable issues across security, performance, tests, architecture, organizational drift, and accessibility.

Core Features & Use Cases

  • Pattern-driven scans surface issues across multiple dimensions and produce evidence-backed findings.
  • Generate standardized investigations with concrete file references and ROI-based prioritization.
  • Use cases include pre-launch health checks, risk triage, and long-term codebase improvements.

Quick Start

Scan the repository for Skill Units and output their metadata in YAML.

Frequently Asked Questions about codebase-audit

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

FAQPage Schema
How do I perform a codebase audit for security and architecture risks?

A codebase audit uses pattern-driven scans across dimensions like security, architecture, and accessibility to surface evidence-backed findings with concrete file references and ROI-based prioritization.

What is the best way to generate a YAML metadata inventory of Skill Units in a repository?

Generating YAML metadata requires verifying SKILL.md at the repository root, parsing its YAML frontmatter for required fields, and outputting a single YAML document containing all valid Skill Unit metadata.

Can I automate codebase investigations for long-term organizational drift and accessibility?

Automated codebase investigations support long-term improvements by systematically scanning for organizational drift and accessibility issues, returning standardized findings with concrete file references.

Does the codebase audit process require worker-base to function?

Yes, the codebase audit requires worker-base as a dependency to execute its pattern-driven scans and generate structured metadata for repository ingestion.

What limitations exist when scanning a repository for valid Skill Units?

Repository scanning is limited to identifying valid Skill Units by verifying SKILL.md and parsing its YAML frontmatter; units missing required fields or the root file will not be enumerated in the output metadata.