repo-orientation

Read REPO_PROFILE.json and git status to map canonical and planned paths.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Vel-Labs/ClearIntent --skill repo-orientation-vel-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-orientation
Source: https://github.com/Vel-Labs/ClearIntent/tree/main/skills/repo-orientation
Command: npx skills add https://github.com/Vel-Labs/ClearIntent --skill repo-orientation-vel-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repo orientation builds a checkout-grounded map before changing files. It should separate implemented truth, documented-only plans, and forbidden early scope.

Core Features & Use Cases

  • Read REPO_PROFILE.json and its readFirstFiles.
  • Confirm the checkout state with git status --short.
  • Identify canonical paths, planned paths, and out-of-scope areas.
  • Run npm run validate:scaffold if the task touches onboarding, governance, templates, docs routing, or quality gates.
  • Report implemented, documented-only, planned, and forbidden early-scope areas separately.
  • Output a concise orientation with current repo state, canonical authority layer, next implementation layer, commands to run, stop conditions, and files likely relevant to the requested task.

Quick Start

Use the repo-orientation skill to map the current state and outline the next actions for safe changes.

Frequently Asked Questions about repo-orientation

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

FAQPage Schema
How do I orient a new team member before making changes to a repository?

Repository orientation builds a checkout-grounded map by reading REPO_PROFILE.json and running git status to separate implemented truth, documented-only plans, and forbidden early-scope areas. It outputs canonical paths, next actions, and stop conditions to safely guide onboarding.

What is the best way to audit a git repository state for early-scope planning?

Repository auditing identifies canonical paths and maps the current repo state using git status --short. It separates implemented areas from documented-only plans and forbidden early-scope regions, providing a concise orientation with commands and stop conditions for safe planning.

How do I separate implemented code paths from documented-only plans during onboarding?

Separating implemented truth from documented-only plans requires reading REPO_PROFILE.json and its readFirstFiles. The orientation process reports implemented, planned, and forbidden areas separately to clarify canonical authority layers and next implementation layers.

Does repo orientation work with governance and scaffolding validation workflows?

Repo orientation works with governance and scaffolding workflows by running npm run validate:scaffold when tasks touch onboarding, templates, docs routing, or quality gates. This confirms the checkout state and validates the scaffolding before changes proceed.

When should I not use an automated repository orientation workflow?

You should not use automated repository orientation when REPO_PROFILE.json is absent or when the task requires modifying forbidden early-scope areas. The workflow relies on existing profile files and canonical paths to safely map implemented truth and planned regions.

Can I use repository orientation to map docs routing and template paths?

Yes, repository orientation maps docs routing and template paths by identifying canonical paths and mapping the current repo state. It triggers validate:scaffold for tasks touching templates or docs routing, outputting relevant files and next implementation actions.