Copilot-Managed-Runtime / CodeFlow
AGENTS.md4 starsChanged 8 days agoMITView on GitHub
CodeFlow is a React + Vite + TypeScript app hosted on Copilot Managed Runtime that reviews GitHub pull requests through the public GitHub connector. Start with README.md. - .github/skills/setup-codeflow/SKILL.md — first-time setup (ms app init, app settings, GitHub connector, .env.local). - .github/skills/add-data-source/SKILL.md — move app data from browser storage to a shared backend. - The sample ships without ms.config.json and connector code generation (generated/, .ms/). Setup creates them (npx ms app init, npx ms app add data-source) in the user's…
- Reads credentials
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,843 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 repository38 other files it gives its agents.
- github-actions/AGENTS.mdAGENTS.md
- plugins/copilot-managed-runtime/AGENTS.mdAGENTS.md
- samples/LearningHub/AGENTS.mdAGENTS.md
- samples/TaskManager/AGENTS.mdAGENTS.md
- add-azuredevopsSkill
- add-backendSkill
- add-data-sourceSkill
- add-dataverseSkill
- add-excelSkill
- add-mcscopilotSkill
- add-office365Skill
- add-office365-usersSkill
- add-onedriveSkill
- add-sharepointSkill
- add-teamsSkill
- add-workiqSkill
- create-appSkill
- delete-appSkill
- deploySkill
- devSkill
- list-appsSkill
- list-connectorsSkill
- playSkill
- share-linkSkill
- shareSkill
- stateSkill
- add-data-sourceSkill
- setup-codeflowSkill
- add-data-sourceSkill
- setup-codeflowSkill
- add-data-sourceSkill
- setup-learninghubSkill
- add-data-sourceSkill
- setup-learninghubSkill
- add-data-sourceSkill
- setup-taskmanagerSkill
- add-data-sourceSkill
- setup-taskmanagerSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
All app-owned data goes through src/storage (collections in src/storage/collections.ts).
- Very specific: line 22
Don't use localStorage, sessionStorage or indexedDB directly, and never edit src/storage/core/ (it is shared, synced code).
- Very specific: line 24
Don't log payloads, identities or connector responses.
- Very specific: line 26
Keep test data synthetic (octo-org/octo-repo#123, octocat, example.com).
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
Agent guide
CodeFlow is a React + Vite + TypeScript app hosted on Copilot Managed Runtime that reviews GitHub
pull requests through the public GitHub connector. Start with README.md.
Skills
.github/skills/setup-codeflow/SKILL.md— first-time setup (ms app init, app settings, GitHub connector,.env.local)..github/skills/add-data-source/SKILL.md— move app data from browser storage to a shared backend.
Rules
- The sample ships without
ms.config.jsonand connector code generation (generated/,.ms/). Setup creates them (npx ms app init,npx ms app add data-source) in the user's copy, which is the app's own repository; they are committed there. Onlysrc/connectors/*may importgenerated/; everything else uses theGitHubClientinterface. - Anything the connector has no REST operation for goes through GraphQL
(
githubClient.graphql, viasrc/services/graphQl.ts). The operation takes no variables: inline values withgqlStringand treat any GraphQLerrorsentry on a mutation as failure. - All app-owned data goes through
src/storage(collections insrc/storage/collections.ts). Don't uselocalStorage,sessionStorageorindexedDBdirectly, and never editsrc/storage/core/(it is shared, synced code). - Don't log payloads, identities or connector responses; use
src/lib/logger.ts. - Render external links through
safeUrl/githubLink. - Keep test data synthetic (
octo-org/octo-repo#123,octocat,example.com).
Checks
npm run lint
npm test
npm run typecheck # after setup (needs generated/)
npm run build # after setupDoes 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.

