orient

To rebuild git context after switching branches, inspect the repository status, diff staged changes, and review recent commits to infer the branch goal. This summarizes the current working state and identifies modified files containing TODO or FIXME markers.

Summarizing your current git repository state involves analyzing branch relationships, unstaged diffs, and recent commit messages. This process identifies changed files and infers the likely development goal to generate a concise working-state brief.

To find incomplete work in your git diff, search modified files for notable markers like TODO, FIXME, HACK, and XXX. Reviewing staged and unstaged changes alongside recent commits helps identify incomplete tests and debug code.

To figure out what a git branch was working on, analyze the recent commit messages and changed files. Reading modified files and checking for debug code or markers allows you to infer the most likely goal of the branch.

Yes, generating a repository status summary works without any dependencies. It directly inspects git status, branch upstream relations, and file diffs to diagnose the repository state and produce a working context brief.

You need to generate a working-state brief when you have cleared context, opened an old branch, resumed work, or asked what state the repo is in. It diagnoses the repository state to quickly reorient you to the current work.