skills.rest
vhqtvn
vhqtvnCOMMUNITY
Explore all skills by this author →
GitHub

repo-recon

Generate and maintain repository structure maps for entrypoints, hotspots, packages, and tests.

8|Updated Jun 18, 2026
Search Tags:#yaml#structure#packages#hotspots#tests#entrypoints#repository mapping
One-click install
npx skills add https://github.com/vhqtvn/vh-solara --skill repo-recon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-recon
Source: https://github.com/vhqtvn/vh-solara/tree/main/.opencode/skills/repo-recon
Command: npx skills add https://github.com/vhqtvn/vh-solara --skill repo-recon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain a reliable structural map of a code repository so agents can quickly find entrypoints, hotspots, package boundaries, and test locations without re-discovering them from scratch.

Core Features & Use Cases

  • Repository Mapping: Identifies the main execution entrypoints, core files, logical packages, and test roots.
  • Structural Refresh: Updates an existing repo-recon data file when the repository layout changes.
  • Repo Orientation: Supports changes that need fast access to the right files, such as debugging, feature work, or test execution planning.

Quick Start

Ask the skill to scan the repository and create or refresh .opencode/repo-configs/repo-recon-data.yml with entrypoints, hotspots, packages, and tests.

Frequently Asked Questions about repo-recon

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

FAQPage Schema
How do I map repository structure to find entrypoints and hotspots?▼

Repository mapping identifies main execution entrypoints, core hotspot files, logical packages, and test roots, preserving them in a YAML orientation file so agents can locate structural boundaries without re-discovering them from scratch.

What is the best way to keep a repository structure map current after layout changes?▼

Structural refresh updates an existing repo-recon data file by re-reading the repository layout, ensuring your orientation file reflects current entrypoints, packages, and tests for accurate change-impact analysis.

How does a repository structure map help with change-impact analysis?▼

Change-impact analysis uses a repository structure map to quickly access relevant entrypoints, hotspots, and test locations, reducing the time spent locating the right files during debugging, feature work, or test execution planning.

Can I use repository mapping for test discovery in large codebases?▼

Repository mapping supports test discovery workflows by identifying test roots and preserving actionable structural metadata, allowing agents to quickly locate test locations alongside logical packages and execution entrypoints.

Do I need any dependencies to generate a repository structure map?▼

Repository mapping requires no external dependencies to generate and maintain a structural map of entrypoints, hotspots, packages, and tests in a YAML configuration file.

When should I refresh my repository structure map?▼

Refresh your repository structure map when the repository layout changes, ensuring the orientation file accurately reflects current entrypoints, hotspots, package boundaries, and test locations for reliable codebase navigation.

Related Skills

Explore More Software Engineering Skills→
velesarvelesar
1

vp-f02-structure

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

Community
Intermediate
tom-xstom-xs

playwright-regression-testing

Plan and optimize Playwright TypeScript regression suites across CI/CD pipelines.

Community
Advanced
maxvaegamaxvaega
146

nested-root-skill

Locate SKILL.md files in nested directories and extract metadata into a catalog.

Community
Basic
realsigridjinrealsigridjin
20

deepinit

Generate and maintain hierarchical AGENTS.md documentation across a codebase.

Community
Advanced