Integrations

Integrations carry the same repository-owned architecture context into agent harnesses, CI, and visualization tools.

Coding-agent skill

yarramate skill install --repo

The maintained skill guides supported agents to orient, author native documents, validate changes, and avoid editing generated output. Durable context stays in the repository, not in a chat session.

GitHub Actions

Run yarramate check in CI so invalid references and documents cannot quietly drift onto the main branch. Pin the version your repository has evaluated.

MCP

The MCP adapter exposes YarraMate operations to compatible clients. It is an access layer over the same workspace, not a separate architecture database.

LikeC4

The LikeC4 adapter projects selected model subjects into diagrams. Mapping files connect stable native identities to external identifiers; diagram output remains derived.

Graphify

Graphify can gather code evidence for discovery and reconciliation. Treat its output as evidence to review, not as an unquestionable architecture model.

Integration boundary

Harnesses and tools may change. Keep the canonical model in .yarramate/, validate it with the CLI, and regenerate tool-specific views from that source.

Return to documentation home →

These adoption guides are maintained by the website team. Read the normative product documentation →