ontology-atlas
Bridges the gap between human architecture understanding and AI agent decision-making, reducing integration errors and unintended side effects when agents mo…
Understand what your codebase builds, why it is structured that way, and what a change could affect. One shared Markdown ontology for humans and coding agents—visualized for people, accessible to agents through MCP, and reviewed with Git. Local-first. Open source.
- Generate a shared codebase map showing system components, dependencies, and their relationships.
- Ask Claude to identify what code changes might affect other parts of your application.
- Document architecture decisions in Markdown that both your team and AI agents can understand.
Bridges the gap between human architecture understanding and AI agent decision-making, reducing integration errors and unintended side effects when agents modify codebases at scale.
Engineering teams adopting agentic coding workflows who need shared, version-controlled system maps.
https://github.com/wlsdks/ontology-atlas
By wlsdks
How to Get It
claude plugins install wlsdks/ontology-atlas
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me generate a shared codebase map showing system components, dependencies, and their relationships
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 86 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 86 GitHub stars; contributors unknown; last commit 0d ago; license MIT.