agentleFS
metagit-aimetagit-ai/metagit-cli/.mex/AGENTS.md

metagit-cli

AGENTS.md4 starsChanged 12 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, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this AGENTS.md into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 38 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    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:

    Never commit secrets, tokens, or credential material into repo-tracked files.

    line 13
  2. Very specific:

    Keep .metagit.yml / config model compatibility intact.

    line 14
  3. Distinctive:

    Keep mutating repo operations explicitly guarded (especially MCP sync modes).

    line 15
  4. Very specific:

    Put business logic in src/metagit/core/*.

    line 16
  5. Distinctive:

    Run lint + relevant tests before claiming a change is complete.

    line 17
  6. Very specific:

    Default commit messages to patch semantics (fix:).

    line 18

“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
AGENTS.md

Metagit CLI

What This Is

Metagit CLI manages and validates repository/workspace metadata (.metagit.yml) and exposes that context to humans and agents, including via MCP runtime tooling.

Non-Negotiables

  • Never commit secrets, tokens, or credential material into repo-tracked files.
  • Keep .metagit.yml / config model compatibility intact; do not bypass validation paths.
  • Keep mutating repo operations explicitly guarded (especially MCP sync modes).
  • Put business logic in src/metagit/core/*; keep CLI command handlers thin.
  • Run lint + relevant tests before claiming a change is complete.
  • Default commit messages to patch semantics (fix:). Use feat: only for additive backward-compatible changes, and use major/breaking prefixes only when schema/config compatibility is intentionally broken.

Commands

  • Setup: ./configure.sh && task install
  • Lint: task lint
  • Format: task format
  • Tests: task test
  • Build: task build
  • MCP runtime: uv run metagit mcp serve --status-once

Scaffold Growth

After every task: if no pattern exists for the task type you just completed, create one. If a pattern or context file is now out of date, update it. The scaffold grows from real work, not just setup. See the GROW step in ROUTER.md for details.

Navigation

At the start of every session, read 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.