domains / families / agent-tooling / agents-md

agents-md

combined

Creates and maintains concise AGENTS.md and CLAUDE.md project instruction files. Use when asked to create AGENTS.md, update AGENTS.md, maintain agent docs, set up CLAUDE.md, document repository agent conventions, or keep coding-agent instructions minimal and reference-backed. Create, revise, or audit AGENTS.md files from repository evidence, verified commands, and correctly scoped instructions without overwriting maintainer intent.

When to use

• The user asks to create, update, shorten, or audit `AGENTS.md`.
• A monorepo needs root instructions plus narrower package-level overrides.
• Existing agent instructions contain stale commands, duplicated policy, or
• The user wants to reconcile `AGENTS.md` with `CLAUDE.md`,

When not to use

• Repository evidence can be incomplete or contradictory; ask when a material
• A documented command may still require credentials, services, or operating
• AGENTS.md support and precedence vary across coding tools; verify the target
• This skill improves instruction quality but cannot prove that every future

Skill page

Conflict

Both copies describe the same task (creating/maintaining AGENTS.md from repository evidence), but they disagree on core constraints and each contains material steps the other lacks. The getsentry copy imposes a hard line limit (under 60, never exceed 100), a fixed default section template, a mandatory CLAUDE.md symlink, and a required Co-Authored-By commit attribution block. The sickn33 copy explicitly rejects a universal line limit, fixed section list, symlink layout, and commit-attribution policy, and instead adds evidence-tracking, preservation of existing maintainer intent, reconciliation with other instruction files, safety boundaries, and a validation/handoff report. Crowning one would hide a real alternative approach.