opensite-ai/opensite-skills / agent-file-engine
agent-file-engine
VerifiedRepository-specific AGENTS.md authoring and maintenance workflow. Use when creating, refreshing, or expanding AGENTS.md coverage for a codebase, including deciding whether nested AGENTS.md files are needed for subsystems with distinct rules, workflows, or AI-sensitive constraints.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.0 KB |
| agents/openai.yaml | config | 402 B |
| examples/coverage-plan.md | markdown | 829 B |
| references/activation.md | markdown | 851 B |
| references/discovery-checklist.md | markdown | 1.3 KB |
| references/nested-coverage-heuristics.md | markdown | 1.5 KB |
| scripts/inventory_agent_scope.py | script | 6.4 KB |
| templates/nested-agents.md | markdown | 634 B |
| templates/root-agents.md | markdown | 1013 B |
references/discovery-checklist.md
View on GitHub# Discovery Checklist
Use this checklist before writing or updating any `AGENTS.md`.
## Repo inventory
- Identify the repo root and whether it is a single project or a workspace.
- List existing `AGENTS.md`, `README.md`, `CLAUDE.md`, and major docs under `docs/`.
- Identify primary manifests:
- `package.json`, `pnpm-workspace.yaml`, `turbo.json`
- `Cargo.toml`
- `Gemfile`
- `pyproject.toml`
- `go.mod`
- Identify major code roots: `src/`, `app/`, `components/`, `packages/`, `apps/`, `lib/`, `services/`, `workers/`, `jobs/`.
## Commands
Find the commands agents will actually need:
- test
- type-check
- lint
- build
- package or export generation
- app-specific smoke checks
Prefer commands from real manifests, CI, or package scripts over guesses.
## High-signal docs
Read the docs that most strongly constrain agent work:
- architecture overviews
- performance or bundle-size rules
- serialization contracts
- migration templates
- auth or deployment docs
- AI/vector/workflow docs
## Hotspots for nested coverage
Look for directories with:
- unique contracts or serialization rules
- AI-specific behavior
- performance-sensitive code
- deployment or infra logic
- background job patterns
- design-system or block-registry rules
If a directory is large but does not have unique rules, keep coverage at the parent level.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |