inits

To generate an AGENTS.md for codebase onboarding, analyze the repository to capture cross-cutting conventions, implicit contracts, and operational constraints, then output a structured guide with explicit rules and workflow guidance for future agents.

You should capture hard-to-rediscover rationale, non-obvious command guidance with hidden constraints like required ordering or env vars, and cross-cutting boundaries that span multiple files to guide future agents effectively.

To update an existing AGENTS.md without losing data, suggest targeted improvements instead of rewriting the file, ensuring every updated statement remains grounded in repository findings and omitting uncertain claims.

Yes, you can document implicit operational contracts and constraints by analyzing the codebase to identify non-obvious command caveats and cross-cutting boundaries, outputting them as explicit rules suitable for agent ingestion.

A key limitation is that every statement in the generated guide must be grounded in repository findings; uncertain claims or unverified rationale are omitted to prevent agents from acting on inaccurate codebase assumptions.