repository-orientation

Maps unfamiliar repositories by tracing entry points, contracts, ownership, and verification lanes before code changes.

2.7k|171|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/compozy/compozy --skill repository-orientation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repository-orientation
Source: https://github.com/compozy/compozy/tree/main/catalog/packages/repository-orientation/skills/repository-orientation
Command: npx skills add https://github.com/compozy/compozy --skill repository-orientation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a task spans multiple packages, public contracts, persistence layers, or runtime wiring in an unfamiliar codebase, editing code without understanding the architecture leads to broken invariants and misplaced changes. This Skill builds an evidence-backed map of the repository before any mutation begins.

Core Features & Use Cases

  • Architecture Mapping: Traces user-visible entry points through contracts, runtime ownership, persistence, and downstream consumers.
  • Ownership & Invariant Identification: Pinpoints the owning layer, canonical test suite, and the narrowest relevant verification lane for a change.
  • Reuse Discovery: Searches for existing primitives and adjacent implementations before proposing new abstractions.
  • Use Case: You are asked to add a feature that touches an API contract and its database layer in a repo you have never seen. Use this Skill to produce a concise orientation covering affected surfaces, call and data flow, invariants, the working file set, and open questions before writing any code.

Quick Start

Use the repository-orientation skill to map this repository and identify the owning layer and verification path for my planned change.

Frequently Asked Questions about repository-orientation

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

FAQPage Schema
How do I understand an unfamiliar codebase before making changes?

Start by reading the repository's instruction files, then trace the user-visible entry point through contracts, runtime ownership, and persistence. Identify the owning layer, invariants, and canonical test suite before editing any code.

How to find the right files to change in a large repository?

Trace the data and call flow from the entry point to downstream consumers, then define a working set of files and commands. Search for existing primitives and adjacent implementations before creating new abstractions.

When should I use repository orientation before coding?

Use it when a task crosses packages, public contracts, persistence, or runtime wiring and the owning architecture is unclear. It is designed for changes where editing without a map risks violating invariants.

What should a codebase orientation report include?

A concise orientation includes the goal and affected surfaces, the authoritative call and data flow, invariants and ownership boundaries, the working set of files and commands, and unresolved questions that materially change implementation.

When is repository orientation not necessary?

It is unnecessary for small, single-file changes where the owning layer and verification path are already obvious. The Skill targets tasks whose scope crosses architectural boundaries.