Ontoly Agent Skills

Analyze JavaScript and TypeScript repositories through a shared Software Graph.

Ontoly’s fourteen-Skill package covers onboarding, architecture, configuration, dependencies, dead code, documentation, impact, migration, performance, refactoring, tracing, SDKs, and security.

Use cases

  • Explore architecture and dependencies
  • Assess change impact and refactoring
  • Review performance or security

How to use

Install Ontoly and build a graph for the repository before analysis. Check graph trust and diagnostics, then use the corresponding Skill with the upstream MCP or CLI.

Skills

  • architecture-review

    Review repository architecture using Ontoly Software Graph and MCP capabilities. Use when asked to explain architecture, module boundaries, package topology, service ownership, or architectural risk.

    0xsarwagya/ontoly
  • codebase-onboarding

    Onboard a developer to a repository using Ontoly graph summaries. Use when asked to explain a new codebase, identify entrypoints, map packages, or suggest first files to inspect.

    0xsarwagya/ontoly
  • configuration-analysis

    Audit configuration and environment variable usage through Ontoly configuration capabilities. Use when asked where env vars, build config, runtime config, or feature flags are read.

    0xsarwagya/ontoly
  • dead-code-analysis

    Find potentially unused functions, methods, services, routes, or features using Ontoly dead-code and entrypoint capabilities. Use when asked what code appears unreachable or safe to remove.

    0xsarwagya/ontoly
  • dependency-analysis

    Analyze internal and package dependencies using Ontoly graph traversal. Use when asked which modules, packages, services, or files depend on each other.

    0xsarwagya/ontoly
  • documentation

    Draft graph-backed documentation from Ontoly summaries and traces. Use when asked to document architecture, APIs, modules, packages, or request lifecycles without re-parsing source files.

    0xsarwagya/ontoly
  • framework-analysis

    Explain detected frameworks and framework-specific graph coverage using Ontoly framework reports. Use when asked whether a repository uses NestJS, Next.js, React, Turborepo, or other supported framework concepts.

    0xsarwagya/ontoly
  • impact-analysis

    Analyze change impact using Ontoly dependency and dependent traversal. Use when asked what breaks if a symbol, service, route, package, or repository node changes or is removed.

    0xsarwagya/ontoly
  • migration-analysis

    Plan migrations using Ontoly architecture, dependency, impact, and configuration evidence. Use when asked to migrate frameworks, packages, APIs, modules, or runtime configuration.

    0xsarwagya/ontoly
  • performance-analysis

    Investigate performance-sensitive architecture using Ontoly call, dependency, and graph statistics evidence. Use when asked about hot paths, expensive flows, or performance investigation starting points.

    0xsarwagya/ontoly
  • refactoring

    Plan refactors with Ontoly impact and dependency evidence. Use when asked to move, rename, split, extract, or remove code while preserving behavior.

    0xsarwagya/ontoly
  • request-tracing

    Trace request lifecycle behavior through Ontoly route, handler, and call graph capabilities. Use when asked to trace login, API, controller, route, or request execution flow.

    0xsarwagya/ontoly
  • sdk-generation

    Plan SDK generation from Ontoly API, route, model, and operation evidence. Use when asked to design or scope SDK generation without implementing code generation in the skill layer.

    0xsarwagya/ontoly
  • security-review

    Review authentication, authorization, and security-sensitive flows using Ontoly graph evidence. Use when asked about auth ownership, protected routes, permissions, guards, or security risk.

    0xsarwagya/ontoly