agentleFS
metagit-aimetagit-ai/metagit-cli/.github/copilot-instructions.md

metagit-cli

Copilot instructions4 starsChanged 11 days agoMITView on GitHub

Always-loaded project anchor. Read this first. Contains project identity, non-negotiables, commands, and pointer to ROUTER.md for full context.

43 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this copilot-instructions.md into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 38 edited versions we read keep these.

  • 6

    Distinctive

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Not a tagline — a factual description of what the software does.

    line 12
  2. Distinctive:

    Never write database queries outside of the repository layer

    line 20
  3. Distinctive:

    Never commit secrets or API keys

    line 21
  4. Distinctive:

    Always handle errors explicitly — no silent failures -->

    line 22
  5. Distinctive:

    Use the actual commands from this codebase — not placeholders.

    line 27
  6. Distinctive:

    After meaningful work, run GROW:

    line 35
  7. Very specific:

    Write: bump last_updated on changed scaffold files and run mex log when rationale matters

    line 39

“Common” is measured: kept by at least 6 in 10 of the 38 edited versions of this file we could read. “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

[Project Name]

What This Is

<!-- One sentence. What does this project do? Length: 1 sentence maximum. Not a tagline — a factual description of what the software does. Example: "A REST API for managing inventory across multiple warehouse locations." -->

Non-Negotiables

<!-- Hard rules the agent must never violate. Not preferences — rules. These are the things that, if broken, cause real damage to the codebase. Length: 3-7 items maximum. More than 7 means the list has not been prioritised. Example: - Never write database queries outside of the repository layer - Never commit secrets or API keys - Always handle errors explicitly — no silent failures -->

Commands

<!-- The exact commands needed to work on this project. Include: run dev server, run tests, run linter, build. Use the actual commands from this codebase — not placeholders. Example: - Dev: `npm run dev` - Test: `npm test` - Lint: `npm run lint` - Build: `npm run build` -->

After Every Task

After meaningful work, run GROW:

  • Ground: what changed in reality?
  • Record: update .mex/ROUTER.md and relevant .mex/context/ files
  • Orient: create or update a .mex/patterns/ runbook if this can recur
  • Write: bump last_updated on changed scaffold files and run mex log when rationale matters

Navigation

At the start of every session, read .mex/ROUTER.md before doing anything else. For full project context, patterns, and task guidance — everything is there.

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.