osdu-spi-stack
Copilot instructions0 starsChanged 42 days agoApache-2.0View on GitHub
AGENTS.md at the repository root is the source of truth for setup, working commands, conventions, and scope rules. Read it first; nothing here repeats it. Skills under .github/skills/ carry the repo's working discipline: - prime orients in the tree at the start of a task. - gh-voice governs the tone of every PR description, issue, and comment. - resolve-review-threads is the loop for addressing review comments on a pull request: verify each finding before changing code, reply with evidence, resolve…
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,343 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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- code-reviewSkill
- gh-voiceSkill
- osdu-apiSkill
- primeSkill
- resolve-review-threadsSkill
The file
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 21
When reviewing a pull request, use the code-review skill and write comments in the gh-voice style.
≈ “Common” is an estimate: at least 1 in 5 of the 3,779 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
AGENTS.md at the repository root is the source of truth for setup, working
commands, conventions, and scope rules. Read it first; nothing here repeats it.
Skills under .github/skills/ carry the repo's working discipline:
primeorients in the tree at the start of a task.gh-voicegoverns the tone of every PR description, issue, and comment.resolve-review-threadsis the loop for addressing review comments on a pull request: verify each finding before changing code, reply with evidence, resolve the thread.code-reviewis the rubric for reviewing pull requests in this repo: the invariants a diff can break silently, and the classes of comment not to leave.osdu-apicalls the OSDU APIs of the connected environment as a seeded identity or as the signed-in person.
Path-scoped rules live in .github/instructions/.
When reviewing a pull request, use the code-review skill and write comments
in the gh-voice style. When addressing review comments, use
resolve-review-threads. When writing a PR description, follow the shape in
CONTRIBUTING.md under "PR Descriptions" and the tone in gh-voice.
Commits and PR titles follow Conventional Commits. Do not add generated-with footers, co-author trailers for tools, or session links to commits, PR descriptions, or comments.
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.