orient-map

Computes the delta since your last look and renders the work trajectory as a path or branch tree.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill orient-map-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orient-map
Source: https://github.com/allemaar/open-skills/tree/main/skills/orient-map
Command: npx skills add https://github.com/allemaar/open-skills --skill orient-map-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When returning to a project, repo, or plan after time away, it is hard to answer "what changed since I last looked?" and "how deep down this branch am I?" without manually digging through git logs, plans, and file trees. This Skill answers those questions with a fresh, read-only sweep that produces the delta since your last-look anchor plus a done → here → next trajectory rendered as a spine on the trunk or a tree on a branch. ## Core Features & Use Cases - Delta-first orientation: Leads with what changed since a caller-supplied or git-inferred anchor, including honest no-change zones and, on a branch, what landed on the trunk while you were away. - Topology detection: Owns branch detection (git, plan-level, or side-quest) and emits cursor, fork point, ahead/behind counts, and trunk reference so sibling skills never recompute them. - Provenance-tiered, fail-closed output: Every field is tagged attested, inferred, or guessed; barren evidence yields an explicit NO SUBSTRATE card instead of a fabricated tree. - Three output faces: Agents receive a structured YON record; humans receive a plain-language markdown read plus a visual widget or information-complete ASCII twin. - Use Case: You return to a feature branch after two hours and ask what changed — the Skill reports 2 commits and 3 files changed, shows the branch tree with your cursor position, notes one commit landed on main since your fork, and flags the inferred rejoin point as the load-bearing guess. ## Quick Start Ask your agent "what changed since my last look and show me the map of this branch" to get the delta and trajectory for the current project.

Frequently Asked Questions about orient-map

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

FAQPage Schema
How do I see what changed in a git repo since my last look?

Invoke the skill with a last-look anchor such as a git ref or HEAD@2h, and it computes the diff since that anchor using a read-only subagent. The output leads with the change set, lists unchanged zones honestly, and shows your done-here-next trajectory.

How do I tell how deep down a branch or side-quest I am?

The skill detects topology from git merge-base, plan sub-phases, or side-quests that never became branches, then renders a tree showing the fork point, branch lane, cursor position, and ahead/behind counts. When no base exists it reports unknown rather than assuming trunk.

What is the difference between orient-map and orient-status?

orient-map reports the shape and the delta — how you got here and what moved. orient-status reports position, remaining work, and a banded ETA on the node you are standing on. They share one sweep's topology, with orient-map owning the branch and fork fields.

Does orient-map work without git or a plan file?

It falls back to conversation and file-mtime evidence, but on barren evidence it fails closed: it renders an explicit NO SUBSTRATE card with an indeterminate gate status instead of fabricating a structural tree. Nothing is stored between calls.

Does orient-map modify my repository or store state?

No. It is strictly read-only: gathering is delegated to a bounded, depth-1 subagent, the last-look anchor is caller-supplied or git-inferred and never written to disk, and every call recomputes from current reality.

When should I not use orient-map?

Do not use it for a raw file listing (your IDE owns that), for phase-by-phase plan quality review (use plan-deep-dive), or for deciding next actions (use reflect or plan-create). It only sees and reports the current shape and delta.