repo-map

Identify functional surfaces, entrypoints, trust boundaries, and ownership clusters in a repository.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/zerAda/RestaurantAgentAutomation --skill repo-map-zerada
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-map
Source: https://github.com/zerAda/RestaurantAgentAutomation/tree/main/.opencode/skills/repo-map
Command: npx skills add https://github.com/zerAda/RestaurantAgentAutomation --skill repo-map-zerada

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill aids in building a clear and detailed repository map, which is crucial for navigating complex project structures and ensuring all components are accounted for.

Core Features & Use Cases

  • Identifies Functional Surfaces: Pinpoints apps, CMS, workflows, infrastructure, databases, scripts, and documentation.
  • Documents Entrypoints: Maps package.json, Dockerfiles, compose files, and CI triggers.
  • Determines Trust Boundaries: Highlights public/private segments and network divisions.
  • Pinpoints High-Risk Areas: Flags items with zero test coverage, manual processes, and known technical debt.
  • Clusters Ownership: Assigns responsibility for each repository component.
  • Use Case: When working on a large-scale project with multiple components, use this Skill to quickly locate and understand each part of the system.

Quick Start

Execute the repo-map skill to generate a high-signal repository map for the current project.

Frequently Asked Questions about repo-map

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

FAQPage Schema
How do I map repository structure to identify functional surfaces and entrypoints?

Mapping repository structure involves identifying functional surfaces like apps and databases, and documenting entrypoints such as Dockerfiles and compose files to optimize project navigation and maintenance.

What is the best way to document trust boundaries and high-risk areas in a repository?

Documenting trust boundaries pinpoints public and private network segments, while flagging high-risk areas highlights items with zero test coverage, manual processes, and known technical debt.

How do I assign ownership clusters for repository components?

Assigning ownership clusters maps responsibility to each repository component, ensuring all functional surfaces are accounted for and maintained by the correct teams.

Does repository mapping require manual input for identifying infrastructure and scripts?

Repository mapping requires no manual input for mapping components, automatically identifying infrastructure, scripts, and documentation to generate a high-signal project map.

When do I need to generate a repository map for project navigation?

Generating a repository map is needed when navigating large-scale projects with multiple components, allowing you to quickly locate and understand each part of the system.

Can I use repository mapping to track CI triggers and package.json entrypoints?

Repository mapping documents entrypoints by mapping package.json files, Dockerfiles, compose files, and CI triggers to provide a comprehensive view of project execution paths.