From agent-skills
Creates and maintains AGENTS.md documentation files that guide AI coding agents through a codebase. Use when adding a significant new feature or directory, changing project architecture, setting up a new project or monorepo, noticing a codebase has no AGENTS.md, or after major refactors that change project structure. Also triggers on "document this for agents", "update agents.md", or "create agents.md".
npx claudepluginhub oryanmoshe/agent-skills --plugin agent-skillsThis skill uses the workspace's default tool permissions.
**AGENTS.md is a README for AI agents.** It tells any AI coding tool — Claude Code, Copilot, Cursor, Codex — how to navigate and work with your codebase. Keep it updated as the project evolves.
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.
AGENTS.md is a README for AI agents. It tells any AI coding tool — Claude Code, Copilot, Cursor, Codex — how to navigate and work with your codebase. Keep it updated as the project evolves.
Create AGENTS.md when:
Update AGENTS.md when:
Do NOT create for:
For monorepos or large projects, use a hierarchical approach:
Root AGENTS.md → Project overview, tech stack, global conventions
├── app/AGENTS.md → App-specific architecture, commands, patterns
│ └── feature/AGENTS.md → Feature-specific extension points
Each tier adds specificity. Agents read from root down to the most relevant file.
# AGENTS.md — [Project or Directory Name]
Brief one-line description of this part of the codebase.
## Commands
\`\`\`bash
npm run dev # Start development server
npm test # Run tests
npm run build # Production build
\`\`\`
## Project Structure
\`\`\`
src/
├── api/ # REST endpoints (~12 files)
├── services/ # Business logic (~8 files)
├── models/ # Data models (~6 files)
└── utils/ # Shared utilities (~4 files)
\`\`\`
## Key Patterns
[Describe the main architectural patterns, data flow, or conventions]
## Boundaries
### Always
- [Pattern to always follow]
- [Convention to always use]
### Never
- [Anti-pattern to avoid]
- [Dangerous operation]
### Ask First
- [Risky change that needs confirmation]
If the project also uses Claude Code, create a CLAUDE.md that imports the AGENTS.md:
@AGENTS.md
## Claude-Specific
- [Any Claude Code-specific instructions, hooks, or skill references]
This avoids duplicating content while adding Claude-specific configuration.
Stale documentation: An outdated AGENTS.md is worse than none. Update it when the code changes.
Too granular: Don't create AGENTS.md for every directory. Only for significant architectural boundaries.
Duplicating README: AGENTS.md is for AI agents, not humans. Focus on what an agent needs to navigate and modify code correctly — commands, patterns, boundaries.