Project Orientation Sweep

Use this skill to build a repo-grounded map before changing code. Scale the sweep to the user's request and the repository size: quick and direct for small projects, lane-based and evidence-driven for large projects.

First Moves

1. Establish boundaries:

   • Run pwd, git rev-parse --show-toplevel, git status --short --branch, and git remote -v when inside a git repo.
   • If the current directory is not a repo, identify nearby independent repos instead of assuming a monorepo.
   • Preserve unrelated dirty work.

2. Capture a cheap inventory:

   • Prefer scripts/project_inventory.sh [path] when available, then follow up with targeted reads.
   • Otherwise use rg --files, git ls-files, top-level manifests, and shallow directory counts.
   • Exclude generated or vendor-heavy directories such as node_modules, target, dist, build, .next, .turbo, .venv, and vendor.