Individual skill

repository-orientation

Map 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.

catalog/packages/repository-orientation/skills/repository-orientation/SKILL.md

Read pinned source

Source commit 14f57173e5cae483392cce90a06098fd04dcfda0

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 3, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 2,858
Repository last updated: Nov 8, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,183 bytes

Read excerpt


# Repository Orientation

Build a compact, evidence-backed map before proposing or editing code.

1. Read the repository and surface-specific instruction files that govern the requested paths.
2. Trace the user-visible entry point through contracts, runtime ownership, persistence, and downstream consumers.
3. Identify the invariant, owning layer, canonical test suite, and narrowest relevant verification lane.
4. Search for existing primitives and adjacent implementations before creating a new abstraction.
5. 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;