init

# AGENTS.md Generator Analyze a codebase and generate a concise, accurate `AGENTS.md` contributor guide. **Target:** the current working directory, unless user provided another folder as input. --- ## Gather Information Collect facts about the repository. **Only record what is actually found — never invent information.** These probes are independent — run them in parallel (e.g., dispatch subagents) when the tooling supports it. ### Repository structure Map the repo structure (3 levels deep, excluding .git, node_modules, dist, build, __pycache__, .venv and other autogenerated folders). This is analysis input — the output AGENTS.md should describe non-obvious architecture, not list directories. Focus on the "big picture" that requires reading multiple files to understand. ### Build & dev commands Extract actual command definitions from the project's build system: `package.json` scripts, `Makefile` targets, `pyproject.toml` scripts, `Cargo.toml` bins/workspace members, `go.mod` module path, `docker-compose.yml` services, etc. ### Coding conventions Check for and record key settings of: - Linter configs - Formatter configs - Type checking (note strict mode if applicable) - Agent rules: `.cursorrules`, `.cursor/rules/`, `.github/copilot-instructions.md` - Pre-commit hooks If agent rules files exist, read and extract the important parts — focus on conventions that matter for code generation, not verbatim content. ### Git history Review the last 20 commits to identif...