client-python
AGENTS.md773 starsChanged 2 months agoApache-2.0View on GitHub
This repository is mostly generated code. Before editing or approving a PR, check the top of the file: If that marker is present, do not hand-edit the file. Changes should be made in the upstream source or generator inputs, then regenerated. The main hand-maintained surface is listed in .genignore. At the repo root, that currently includes files such as: There are also package-specific ownership files: If a file is not listed in the relevant .genignore and it has the generated…
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,774 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 repositoryOne other file it gives its agents.
- modelsSkill
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
Before editing or approving a PR, check the top of the file:
- Distinctive: line 11
If that marker is present, do not hand-edit the file.
- Very specific: line 30
If a file is not listed in the relevant .genignore and it has the generated header, assume it should not be edited directly.
- Very specific: line 34
Prefer PRs that change hand-owned files listed in .genignore.
- Distinctive: line 36
If a generated file changed, look for the corresponding source/config change that explains the regeneration.
≈ “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
Repository Guide
This repository is mostly generated code.
Before editing or approving a PR, check the top of the file:
"""Code generated by Speakeasy (https://speakeasy.com). DO NOT EDIT."""If that marker is present, do not hand-edit the file. Changes should be made in the upstream source or generator inputs, then regenerated.
What We Own
The main hand-maintained surface is listed in .genignore.
At the repo root, that currently includes files such as:
pyproject.tomlexamples/*utils/*src/mistralai/extra/*scripts/prepare_readme.py
There are also package-specific ownership files:
packages/gcp/.genignorepackages/azure/.genignore
If a file is not listed in the relevant .genignore and it has the generated header, assume it should not be edited directly.
PR Review Rule Of Thumb
- Prefer PRs that change hand-owned files listed in
.genignore. - Be skeptical of direct edits to generated SDK files under
src/,docs/, orpackages/*/src/. - If a generated file changed, look for the corresponding source/config change that explains the regeneration.
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.