agents-md
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/sentry-skills
code-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.
109security-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.
47find-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.
41commit
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.
18skill-scanner
Scan agent skills for security issues. Use when asked to "scan a skill",
18skill-writer
Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill", "synthesize sources into a skill", "improve a skill from positive/negative examples", "update a skill", or "maintain skill docs and registration". Handles source capture, precision passes, authoring, registration, and validation.
18