Repo orient

Skill contextosai/skills/skills/repo-orient

A collection of Agent Skills — self-contained folders that teach AI agents to perform specialized tasks. Includes a production-readiness harness-audit skill, a plugin marketplace, a SKILL.md spec, and CI validation.

Install

npx -y skills add contextosai/skills --skill repo-orient

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Map an unfamiliar software repository from code and configuration. Use when Codex needs to understand a new codebase, locate entry points or ownership boundaries, explain architecture and runtime flow, identify where a change belongs, or prepare for implementation without yet modifying files. Produce an evidence-backed repository map, not a directory listing or README paraphrase.

SKILL.md

2.3 KB, as published. Nobody here has run it

Repository Orientation

Build the smallest accurate mental model needed for the user's task.

Protocol

Read applicable AGENTS.md files and inspect git status. Treat existing changes as user work.
Inventory with rg --files, bounded by relevant top-level directories. Identify manifests, lockfiles, build/test config, deployment config, and generated/vendor boundaries.
Infer the repository shape: application, library, monorepo, service set, plugin, infrastructure, or hybrid. Verify the inference from manifests.
Trace one real execution path from an external entry point to its terminal effect. Follow imports/calls, configuration, persistence, and outbound I/O; do not infer architecture from names alone.
Trace the requested concern separately. Locate its definition, runtime wiring, tests, and operational surface. Search symbols and call sites before reading entire large files.
Identify boundaries that constrain a change: public API, data/schema, process/service, trust/authorization, transaction, concurrency, and release.
Stop when the model answers the user's question. Do not exhaustively catalog unrelated modules.

Evidence discipline

Cite concrete path:line references for important claims.
Distinguish observed facts from inferences. State what would falsify an inference when uncertainty matters.
Treat README and diagrams as orientation leads, then reconcile them with executable code and configuration.
Call out stale, duplicated, dead, generated, or bypassed paths.
If multiple entry points differ materially, map each relevant path rather than inventing one universal flow.

Output

Use references/repository-map.md. Lead with the answer the user needs, then give the execution path, boundaries, change location, and open questions. Skip sections that add no decision value.

Do not edit the repository unless the user also requests a change.