agents-md
Create and maintain minimal, high-signal agent documentation under 60 lines.
- Enforces research-backed best practices for agent-facing docs; instruction quality degrades with length
- Requires three core sections: Package Manager, File-Scoped Commands (per-file test/lint/typecheck), and Commit Attribution with agent identity
- Analyzes project structure (lock files, linter configs, CI commands, monorepo indicators) to determine what belongs in the file
- Uses headers and bullets only; references existing docs instead of duplicating linter rules or project conventions
- Omits obvious instructions, explanations, and filler; trusts agent capabilities and focuses on project-specific patterns
Maintaining AGENTS.md
Goal: concise, actionable agent instructions. Target under 60 lines; never exceed 100.
Workflow
- Inspect before writing:
- package manager: lock files and manifests
- commands:
package.json,Makefile, task runners, CI workflows - docs/specs/policies:
README.md,CONTRIBUTING.md,docs/,specs/,policies/,SECURITY.md,.github/ - conventions: current code patterns, test layout, generated files, legacy areas to avoid
- Choose scope:
- root
AGENTS.md: repo-wide defaults - nested
AGENTS.md: only when a subtree has different commands or rules - closest instruction file wins; keep narrower files shorter than root files
- root
- Write the smallest useful file.
- Verify exact paths and commands exist.
File Setup
More from getsentry/skills
security-review
Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.
5.3Kcode-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
4.3Kfind-bugs
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.
2.4Kcode-review
Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
2.2Kcommit
ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.
2.0Kiterate-pr
Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.
1.9K