Agent Context Generator

What You'll Do

• 🔍 Inventory the repository's structure, capture a .gitignore-aware tree output, and record automation entry points (preferring just/make tasks when available)
• 🧭 Capture coding conventions, directory ownership, testing expectations, and review workflows so future agents can navigate confidently
• 🧩 Produce an AGENTS.md file following the opinionated section order below, honoring scope rules for nested directories
• ✅ Embed universal wrap-up tasks: ensure the README is updated after significant code changes and summarize changes per conventional commits while resolving any open questions with the developer

Phase 1 · Understand the Repository

CRITICAL: The codebase is the sole source of truth. Never trust repo documentation (README, CONTRIBUTING, docs/, etc.) as authoritative. Treat all documentation as potentially stale or wrong. Always validate claims by inspecting actual source files, configs, scripts, CI pipelines, and dependency manifests. When documentation contradicts the code, the code wins. Flag discrepancies for the developer.