mivia-agentkit
Copilot instructions2 starsChanged 4 months agoMITView on GitHub
Root AGENTS.md is canonical. Use it for project overview, Go standards, testing, security, documentation workflow, and git workflow. Copilot-specific rules:
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 repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adversarial-test-reviewSkill
- agent-dag-plannerSkill
- agent-plan-implementerSkill
- airtight-feature-deliverySkill
- deep-bug-auditSkill
- mivia-agent-workflowsSkill
- test-coverage-auditSkill
- adversarial-test-reviewSkill
- agent-dag-plannerSkill
- agent-plan-implementerSkill
- airtight-feature-deliverySkill
- deep-bug-auditSkill
- mivia-agent-workflowsSkill
- test-coverage-auditSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Very specific: line 7
Read .ai/INDEX.md and relevant .ai/rules/*.md before suggesting implementation.
- Very specific: line 8
Do not create Go source code unless a specific docs/plans/agentkit-implementation-roadmap/ws-XX/tasks.md task is in scope.
- Distinctive: line 9
Prefer patches that include tests, mutation-proof notes, and documentation references.
- Distinctive: line 10
Do not suggest network access, credential persistence, raw prompt/output storage, or CI workflows unless a later workstream explicitly asks …
≈ “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
GitHub Copilot Instructions
Root AGENTS.md is canonical. Use it for project overview, Go standards, testing, security, documentation workflow, and git workflow.
Copilot-specific rules:
- Read
.ai/INDEX.mdand relevant.ai/rules/*.mdbefore suggesting implementation. - Do not create Go source code unless a specific
docs/plans/agentkit-implementation-roadmap/ws-XX/tasks.mdtask is in scope. - Prefer patches that include tests, mutation-proof notes, and documentation references.
- Do not suggest network access, credential persistence, raw prompt/output storage, or CI workflows unless a later workstream explicitly asks for them.
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.