codebase-recon

Reconstruct codebases into canonical YAML artifacts for agent ingestion.

80|2|Updated May 14, 2026

Search Tags:#architecture #codebase #yaml #governance #artifacts #reconstruct

Ready to run

npx skills add https://github.com/PriNova/pi-agent-codebase-workflows --skill codebase-recon-prinova

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codebase-recon
Source: https://github.com/PriNova/pi-agent-codebase-workflows/tree/main/skills/codebase-recon
Command: npx skills add https://github.com/PriNova/pi-agent-codebase-workflows --skill codebase-recon-prinova

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconstruct unfamiliar or undocumented codebases into canonical YAML artifacts, enabling agent-first ingestion and eliminating reliance on prose documentation.

Core Features & Use Cases

Convert codebase knowledge into structured artifacts (architecture, data, constraints) that can be validated and evolved with policy-driven workflows.
Produce repository-scoped artifacts for governance, risk assessment, and automation, not human-facing Markdown.
Use Case: When onboarding a new codebase, run this skill to generate a complete YAML artifact set that captures intent, dependencies, and risk signals for downstream reviews.

Quick Start

Invoke codebase-recon to generate canonical YAML artifacts for a given repository.

Frequently Asked Questions about codebase-recon

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

FAQPage Schema

How do I convert an undocumented codebase into structured YAML artifacts for agent ingestion?▼

To convert an undocumented codebase into YAML artifacts, you can reconstruct it into canonical, repository-scoped YAML files that capture architecture and dependencies. This eliminates reliance on prose documentation for agent-first ingestion.

What is the best way to generate architecture and governance artifacts from an unfamiliar code repository?▼

Generating architecture and governance artifacts from an unfamiliar repository is best achieved by reconstructing the codebase into structured YAML. This applies artifact schemas to capture intent, dependencies, and risk signals for automated policy-driven workflows.

Can I use YAML artifacts for repository-scoped governance and risk assessment instead of Markdown documentation?▼

Yes, you can use YAML artifacts for repository-scoped governance and risk assessment. Reconstructing a codebase produces canonical YAML artifacts designed for automation and validation rather than human-facing Markdown documentation.

Does codebase-recon enforce deterministic formatting and reference integrity for generated YAML artifacts?▼

Yes, codebase-recon enforces deterministic envelope formatting, stable IDs, and reference integrity for generated YAML artifacts. It applies structured artifact schemas and enforces repository-scoped layout rules using shared schemas.

How to onboard a new codebase by capturing dependencies and risk signals into structured artifacts?▼

To onboard a new codebase and capture dependencies into structured artifacts, run a reconstruction process to generate a complete canonical YAML artifact set. This captures intent and risk signals for downstream reviews and agent ingestion.