qvac
AGENTS.md697 starsChanged 18 days agoApache-2.0View on GitHub
Use the active workflows, actions, and validation scripts as the source of truth. Do not duplicate current matrices, runner labels, workflow counts, action versions, or required-check configuration in agent instructions. Read the relevant references before changing CI: - ../docs/ci/LABELS.md for labels and fork trust. - ../docs/ci/MERGE-GUARD.md for required-check wiring. - ../docs/ci/SELF-HOSTED-RUNNERS.md for persistent runners and workspace cleanup. - ../docs/ci/TEAMS.md for approval ownership. - ../docs/ci/MOBILE-ON-DEMAND.md for dispatching addon mobile (Device Farm) tests and choosing the prebuild source. - ../docs/agent-automation.md for automation…
We split this AGENTS.md into the rules it gives an agent
7 rules. About 1 is common, 6 are distinctive, and 0 are very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Use the active workflows, actions, and validation scripts as the source of truth.
- Distinctive: line 4
Do not duplicate current matrices, runner labels, workflow counts, action versions, or required-check configuration in agent instructions.
- Distinctive: line 7
Read the relevant references before changing CI:
- Distinctive: line 18
When editing workflows or composite actions:
- Common: line 22
Treat fork-controlled code and metadata as untrusted, and never expose secrets to untrusted pull-request execution.
- Distinctive: line 27
Follow the documented cleanup pattern for persistent self-hosted runners.
- Distinctive: line 28
Run the narrowest relevant workflow linter and script tests before handoff.
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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
GitHub and CI guidance
Use the active workflows, actions, and validation scripts as the source of truth. Do not duplicate current matrices, runner labels, workflow counts, action versions, or required-check configuration in agent instructions.
Read the relevant references before changing CI:
../docs/ci/LABELS.mdfor labels and fork trust.../docs/ci/MERGE-GUARD.mdfor required-check wiring.../docs/ci/SELF-HOSTED-RUNNERS.mdfor persistent runners and workspace cleanup.../docs/ci/TEAMS.mdfor approval ownership.../docs/ci/MOBILE-ON-DEMAND.mdfor dispatching addon mobile (Device Farm) tests and choosing the prebuild source.../docs/agent-automation.mdfor automation safety.
When editing workflows or composite actions:
- Pin third-party actions to full commit SHAs and retain a readable version comment.
- Declare the least permissions needed. Prefer OIDC to long-lived credentials.
- Treat fork-controlled code and metadata as untrusted, and never expose secrets to untrusted pull-request execution.
- Quote shell inputs and pass untrusted values through environment variables rather than interpolating them into scripts.
- Preserve the repository's merge-guard architecture when adding a gating job.
- Follow the documented cleanup pattern for persistent self-hosted runners.
- Run the narrowest relevant workflow linter and script tests before handoff.
Rewrite CI documentation in place when behavior changes. Do not append corrective notes that leave obsolete instructions active.
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 28,693 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 repository56 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agent-integrations.mdcCursor rule
- .cursor/rules/cpp/string-api-conventions.mdcCursor rule
- .cursor/rules/devops/main.mdcCursor rule
- .cursor/rules/no-remote-code-execution.mdcCursor rule
- .cursor/rules/qip-triage.mdcCursor rule
- .cursor/rules/sdk/commit-and-pr-format.mdcCursor rule
- .cursor/rules/sdk/error-handling.mdcCursor rule
- .cursor/rules/sdk/first-class-product-parity.mdcCursor rule
- .cursor/rules/sdk/main.mdcCursor rule
- .cursor/rules/sdk/public-constants-contract.mdcCursor rule
- .cursor/rules/sdk/request-lifecycle-primitives.mdcCursor rule
- .cursor/rules/sdk/sdk-pod-packages.mdcCursor rule
- .cursor/rules/sdk/skill-authoring-guidelines.mdcCursor rule
- cpp-string-api-reviewSkill
- qv-addon-changelogSkill
- qv-addon-pr-createSkill
- qv-addon-release-notesSkill
- qv-agent-stack-syncSkill
- qv-asana-syncSkill
- qv-daily-work-updateSkill
- qv-dev-diary-setupSkill
- qv-dev-diarySkill
- qv-devops-daily-updateSkill
- qv-devops-pr-createSkill
- qv-devops-pr-reviewSkill
- qv-devops-pr-statusSkill
- qv-devops-runner-queueSkill
- qv-devops-why-my-pr-notSkill
- qv-docs-solution-createSkill
- qv-docs-updateSkill
- qv-holepunch-devSkill
- qv-merge-guard-wireSkill
- qv-mobile-test-dispatchSkill
- qv-notice-generateSkill
- qv-pr-mineSkill
- qv-pr-reviewSkill
- qv-pr-testSkill
- qv-qip-createSkill
- qv-qip-reviewSkill
- qv-qip-triageSkill
- qv-quality-reportingSkill
- qv-registry-autobase-patternsSkill
- qv-release-trainSkill
- qv-sdk-backmergeSkill
- qv-sdk-changelogSkill
- qv-sdk-e2e-createSkill
- qv-sdk-inference-versionSkill
- qv-sdk-pr-createSkill
- qv-sdk-pr-statusSkill
- qv-sdk-update-modelsSkill
- qv-skill-listSkill
- setupSkill
- setupSkill
- qv-nx-ciSkill
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.

