otel-arrow
Copilot instructions444 starsChanged 8 months agoApache-2.0View on GitHub
See AGENTS.md for build, test, and contribution conventions, including changelog entries, ASCII-only Rust source, and test documentation. When reviewing changes under rust/, follow the project's review guide, [AI-Assisted Pull Request Review][review-guide]. It defines what matters in an OTAP Dataflow review: architectural invariants, runtime and performance characteristics, bounded resources, backpressure, correctness, semantic fidelity, test adequacy, and security. The highest-signal rules are restated as path-specific instructions in .github/instructions, which apply automatically to matching files. Report only risks supported by the diff, nearby…
We split this copilot-instructions.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 8
When reviewing changes under rust/, follow the project's review guide, [AI-Assisted Pull Request Review][review-guide].
≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions 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
Copilot Instructions for otel-arrow
See AGENTS.md for build, test, and contribution conventions, including changelog entries, ASCII-only Rust source, and test documentation.
Reviewing pull requests
When reviewing changes under rust/, follow the project's review guide,
AI-Assisted Pull Request Review. It defines what matters in an
OTAP Dataflow review: architectural invariants, runtime and performance
characteristics, bounded resources, backpressure, correctness, semantic
fidelity, test adequacy, and security.
The highest-signal rules are restated as path-specific instructions in .github/instructions, which apply automatically to matching files.
Report only risks supported by the diff, nearby code, or project guidance, and avoid stylistic nitpicks unless they affect correctness, readability, or maintainability.
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,297 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.
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.