situate-situational-awarenesslisted

# Situational awareness Establish what is going on in a repository before acting in it: what the branch does, how far along it is, what its pull request and tickets ask for, and what the project's own rules require of the work. Two reference files carry the parts that must not drift between this skill and `/situate`: - `references/situation-sweep.md` — the six evidence layers, how each one degrades, and the read-only contract. - `references/prior-conversations.md` — when searching local AI transcripts is warranted, how to scope it, and what may not appear in the report. A bare "huh" or "what?" is not this skill. That is disorientation looking for five lines, and the `brief` skill answers it; the `situate-what` skill is its explicit form. This one runs when someone can already say what they want caught up on and wants the whole picture. ## Core principle Read everything before reporting anything. The layers reinterpret each other. A ticket's acceptance criteria change what the diff means. An unresolved review thread explains a commit that otherwise looks like a detour. Reporting each layer as it arrives produces a list of facts; reading them together produces a situation. ## Read-only No commits, no pushes, no edits, no branch switches, no `git fetch`. This runs at the start of a session, before the user has decided anything. A command that mutates while claiming to orient is worse than no command at all — it changes the state being reported on, and it does so