agentleFS
Sign inStart free
HLIntelHLIntel/Headron/.github/copilot-instructions.md

Headron

Copilot instructions3 starsChanged 13 days agoMITView on GitHub

The rules are generated, not written here. Read AGENTS.md — it is produced from atlas.yaml and the tree by python scripts/atlas.py index --write, and atlas.py check fails when it drifts. This file exists because Copilot reads this path, and it stays a pointer so there is no fourth copy of the same body. 1. Route before you read. python scripts/atlas.py route <path> --json gives the language pack, its operating card, its tool manifest, the label, the branch lane and the…

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. HLIntel/thea-software★ 3100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • 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,349 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 repository9 other files it gives its agents.

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
  1. Very specific:

    The rules are generated, not written here: Read AGENTS.md — it is produced from atlas.yaml and the tree by python scripts/atlas.py index …

    line 3

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

Copilot instructions

The rules are generated, not written here. Read AGENTS.md — it is produced from atlas.yaml and the tree by python scripts/atlas.py index --write, and atlas.py check fails when it drifts. This file exists because Copilot reads this path, and it stays a pointer so there is no fourth copy of the same body.

The three things worth repeating here

  1. Route before you read. python scripts/atlas.py route <path> --json gives the language pack, its operating card, its tool manifest, the label, the branch lane and the gates. Reading this repository breadth-first is the failure it exists to prevent.
  2. Never type a count, a date or a tool name into prose. Counts are generated, claims are stamped with a contract version, and a tool's name lives in languages/<route>/tools.yaml where an instrument can check it. Each of those is enforced, and each has a planted defect in scripts/atlas_test.py proving the check still bites.
  3. Verify on the exit code. python scripts/atlas.py check is the verdict; a suggestion that looks right and fails the contract is a failing change. Suggested code for a pull request must also satisfy the gate for its change class — the classes are generated into docs/VERIFY.md.

Copilot code review is a second opinion, never the gate. The required checks are Contract, Dependency Review and the two CodeQL analyses, declared in config/github-controls.json and compared by python scripts/ghaudit.py.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free