vp-f02-structure

Map codebase structure by identifying root layout, source roots, test roots, and configuration patterns.

1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/velesar/alpha-zero-review- --skill vp-f02-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vp-f02-structure
Source: https://github.com/velesar/alpha-zero-review-/tree/main/skills/vp-f02-structure
Command: npx skills add https://github.com/velesar/alpha-zero-review- --skill vp-f02-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill maps a project's structure by identifying source roots, test locations, and key configuration patterns to improve code navigation, audits, and maintenance.

Core Features & Use Cases

  • Root layout detection across monorepos, single-apps, and multi-package setups to tailor analysis and tooling.
  • Source and test root identification across languages and frameworks to improve navigation and impact analysis.
  • Configuration and entry-point discovery to surface important files (configs, manifests, startup scripts) for onboarding and review.

Quick Start

Run VP-F01 to verify prerequisites, then execute VP-F02 steps to analyze a repository's structure.

Frequently Asked Questions about vp-f02-structure

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

FAQPage Schema
How do I analyze project structure to identify source and test roots?

Analyzing project structure involves mapping the root layout and detecting source roots and test roots to improve code navigation and impact analysis. This process identifies configuration patterns and entry points across multi-language repositories.

Can I map the root layout of a monorepo or multi-package setup automatically?

Yes, you can map the root layout of a monorepo or multi-package setup automatically. Root detection applies across single-apps and multi-package configurations to tailor analysis and enable targeted navigation.

What is the best way to discover configuration files and entry points in a codebase?

The best way to discover configuration files and entry points is to analyze the codebase structure, surfacing important files like manifests, configs, and startup scripts to aid onboarding and review workflows.

How do I identify test root locations across different programming languages?

Test root identification works across multiple languages and frameworks by analyzing the repository structure. It maps test locations to improve navigation, audits, and maintenance within diverse codebases.

Does this project structure analysis apply to multi-language repositories?

Yes, project structure analysis applies to multi-language repositories. It maps source roots, test locations, and configuration patterns across various frameworks to support downstream tooling and governance.

Why do I need to map configuration patterns and root layout for codebase audits?

Mapping configuration patterns and root layout is necessary for codebase audits to surface key files and enable targeted navigation. This structural visibility improves maintenance and supports downstream review workflows.