rhdh
AGENTS.md172 starsChanged 22 days agoApache-2.0View on GitHub
Issues live in Jira (RHIDP), not GitHub; fullsend drives agentic execution on GitHub PRs. Read docs/agents/issue-tracker.md before creating, searching, or updating issues. Triage applies the five-role label vocabulary in docs/agents/triage-labels.md as Jira labels. Domain vocabulary lives in GLOSSARY.md; decisions in docs/adr/. Read docs/agents/domain.md before exploring the codebase. CONTEXT.md holds high-level orientation and an index into docs/agents/knowledge/ (detailed topics). Skills live in .agents/skills/. All agent-facing material lives in four places: this file (pointers), CONTEXT.md (orientation), docs/agents/ (config and knowledge), .agents/skills/ (skills).…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository11 other files it gives its agents.
- e2e-deploy-rhdhSkill
- e2e-diagnose-and-fixSkill
- e2e-parse-ci-failureSkill
- e2e-reproduce-failureSkill
- e2e-submit-and-reviewSkill
- e2e-verify-fixSkill
- fix-e2eSkill
- patch-backstageSkill
- pr-review-prioritizerSkill
- pr-triageSkill
- trigger-nightly-jobSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
All agent-facing material lives in four places: this file (pointers), CONTEXT.md (orientation), docs/agents/ (config and knowledge), …
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agents
Agent skills
Issue tracker
Issues live in Jira (RHIDP), not GitHub; fullsend drives agentic execution on GitHub PRs. Read docs/agents/issue-tracker.md before creating, searching, or updating issues.
Triage labels
Triage applies the five-role label vocabulary in docs/agents/triage-labels.md as Jira labels.
Domain docs
Domain vocabulary lives in GLOSSARY.md; decisions in docs/adr/. Read docs/agents/domain.md before exploring the codebase.
Repo knowledge
CONTEXT.md holds high-level orientation and an index into docs/agents/knowledge/ (detailed topics). Skills live in .agents/skills/.
Agent-facing material
All agent-facing material lives in four places: this file (pointers), CONTEXT.md (orientation), docs/agents/ (config and knowledge), .agents/skills/ (skills). Bring a new harness in by pointing it at these files. New detailed knowledge goes in its own file under docs/agents/knowledge/, indexed from CONTEXT.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.