open-bridge
Copilot instructions13 starsChanged 13 days agoMITView on GitHub
GitHub Copilot reads this .github/copilot-instructions.md at session start. This project keeps its full, tool-agnostic operating manual in AGENTS.md — the canonical and complete reference (no further hops). GEMINI.md is the same kind of thin pointer; Claude Code reads AGENTS.md directly. If you are GitHub Copilot: read AGENTS.md and follow it. Then read identity/agent/IDENTITY.md, identity/agent/SOUL.md, identity/agent/INSTANCE.md and docs/families.md if they exist (AGENTS.md § Loaded with this file); Copilot does not resolve its @ lines. Skills are auto-discovered under .github/skills/ — a…
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 repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/board-pilot/references/agents.mdAGENTS.md
- a2aSkill
- archiveSkill
- board-pilotSkill
- bridge-auditSkill
- bridge-contributeSkill
- bridge-curatorSkill
- bridge-explorerSkill
- bridge-greetingSkill
- bridge-leak-checkSkill
- bridge-learnSkill
- bridge-onboardSkill
- bridge-overlaySkill
- bridge-promoteSkill
- bridge-statusSkill
- bridge-syncSkill
- briefingSkill
- calendarSkill
- capability-brokerSkill
- channelSkill
- cmuxSkill
- cockpitSkill
- dashboardSkill
- debriefSkill
- doc-systemSkill
- github-projects-managerSkill
- html-canvasSkill
- html-slidesSkill
- knowledge-repo-initSkill
- mail-draftSkill
- mandantsSkill
- meeting-transcriptionSkill
- object-storeSkill
- onboard-simSkill
- remoteSkill
- scheduleSkill
- secretsSkill
- spec-kickoffSkill
- task-close-postmortemSkill
- tmuxSkill
- tracker-syncSkill
- workloadSkill
- workspaceSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
If you are GitHub Copilot: read AGENTS.md and follow it.
- Very specific: line 28
Before acting on a fresh clone, read rules/session-start.md (Phase 0).
≈ “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
The Bridge — GitHub Copilot
GitHub Copilot reads this .github/copilot-instructions.md at session start.
This project keeps its full, tool-agnostic operating manual in
AGENTS.md — the canonical and complete reference (no further
hops). GEMINI.md is the same kind of thin pointer; Claude Code reads
AGENTS.md directly.
If you are GitHub Copilot: read AGENTS.md and follow it.
Then read identity/agent/IDENTITY.md, identity/agent/SOUL.md,
identity/agent/INSTANCE.md and docs/families.md if they exist (AGENTS.md
§ Loaded with this file); Copilot does not resolve its @ lines.
Skills are auto-discovered under .github/skills/ — a symlink to the top-level
skills/ folder, so every supported agent loads the same skill set.
Run setup once (fresh clone)
A plain git clone does not arm the repo's guard rails. Before your first
commit, run ./bin/setup once (Windows: bin\setup.ps1). It:
- arms the
pre-pushleak guard viagit config core.hooksPath scripts/hooks(blocks publishing local user data to a public upstream), and - repairs the skills-discovery symlinks if your checkout materialized them as plain files.
Session-start gate
Before acting on a fresh clone, read rules/session-start.md
(Phase 0). It detects branch/config state and, for a new user, opens the
onboarding front door.
Copilot has no Skill tool or slash-commands, so to onboard, read
skills/bridge-onboard/SKILL.md →
skills/bridge-onboard/references/workflow.md
and run the phases inline.
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.