Megamono

EXISTING REPOSITORIES

Adopt an existing workspace

Survey first, resolve only real ambiguity, and bring Megamono into a repository without erasing its history.

01

See what is already there

The survey inventories Nx projects, project types, platforms, documentation, toolchains, workflows, and generated surfaces without changing the repository.

bash
megamono init --survey

02

Choose how projects fit together

If Megamono cannot identify a project or document, review its question and supply the requested mapping. This lets you keep the structure and ownership your team already understands.

03

Start small and review the changes

Choose the modules you need, preview the changes, and keep existing workflows that already work for your team. Run your tests and builds before committing the adoption.

megamono.json records exactly what the repository adopted

text
"adoption": {
  "modules": [
    "docs", "agents", "ci",
    "lint", "skills", "health", "inference"
  ],
  "reductions": [],
  "ratchets": []
}
← All guides

Megamono

One repository system for the applications, tools, and people building together inside it.

BUILD

Get startedGuidesDocumentationCLI referenceCapabilitiesInference

SOURCE

GitHub ↗

MIT licensed

© 2026 Megamono

By

Commune Software