Repository Orientation
SkillProductivityMap an unfamiliar repository before changing it. Use when a task crosses packages, public contracts, persistence, runtime wiring, or verification lanes and the owning architecture is not yet clear.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Repository Orientation skill
What this skill tells your AI
The instructions your AI receives, as published by compozy/compozy in catalog/packages/repository-orientation/skills/repository-orientation/SKILL.md and read by ahel’s review.
Build a compact, evidence-backed map before proposing or editing code.
- Read the repository and surface-specific instruction files that govern the requested paths.
- Trace the user-visible entry point through contracts, runtime ownership, persistence, and downstream consumers.
- Identify the invariant, owning layer, canonical test suite, and narrowest relevant verification lane.
- Search for existing primitives and adjacent implementations before creating a new abstraction.
- Record uncertainty explicitly; distinguish confirmed code paths from assumptions.
Return a concise orientation with:
- the goal and affected surfaces;
- the authoritative call and data flow;
- invariants and ownership boundaries;
- the working set of files and commands;
- unresolved questions that materially change implementation.
Do not begin a mutation until the map identifies the owner and a verification path.
Signals
- GitHub stars
- 3k
- Forks
- 177
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
repository-orientation- Source
- github.com/compozy/compozy