agent-startup-context-gate

To verify a repository before coding, confirm the working directory matches the intended project by checking the git remote, README landmarks, and instruction files. This prevents starting work in the wrong repository or against stale context.

Stale context causes issues when resuming coding sessions because the working directory may no longer reflect the intended project state. Verifying repository identity and reading governing instruction files prevents expensive mistakes from outdated assumptions.

The best way to check repository identity is to verify the git remote, confirm README landmarks, read instruction files, and review status docs. This ensures the working directory is truly the target project before any code changes occur.

Yes, you can use instruction files and canonical status docs to validate a project path safely. Reading these governing documents before any code changes separates verified facts from assumptions and missing information.

A startup context report for repository verification should include facts, assumptions, and missing information. It confirms the working directory matches the intended project using git remote, README identity, landmarks, and recent history.

You need to validate your working directory before writing code during repository startup, resumed sessions, or any situation where context may be stale. Checking git remote and instruction files prevents working in the wrong repository.