ad-graph

Generate static class hierarchy, call graph, CFG, and package graphs from compiled class output.

3|Updated May 10, 2026
One-click install
npx skills add https://github.com/Acendas/android-debugger --skill ad-graph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ad-graph
Source: https://github.com/Acendas/android-debugger/tree/main/skills/ad-graph
Command: npx skills add https://github.com/Acendas/android-debugger --skill ad-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate clear, static representations of Android/Java/Kotlin code structure from compiled output, enabling quick reasoning about inheritance, call paths, and module organization without running the app.

Core Features & Use Cases

  • Class hierarchy: reveal superclasses and implemented interfaces for a given class.
  • Call graph: identify which methods call a target and which are invoked from it.
  • CFG and package graph: inspect control-flow graphs and package organization for holistic understanding.
  • Output formats: render diagrams in ASCII for terminals or Mermaid for documentation.

Quick Start

Request a graph for a target class or method to generate the corresponding static diagram from the compiled output.

Frequently Asked Questions about ad-graph

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a static call graph for Java or Kotlin projects?

To generate a static call graph for Java or Kotlin projects, provide the compiled class directories to analyze method calls and render the output as ASCII or Mermaid diagrams without running the application.

Can I visualize a class hierarchy from compiled Android output?

Yes, you can visualize a class hierarchy from compiled Android output by specifying the target class and class directory to reveal superclasses and implemented interfaces.

What is the best way to create Mermaid diagrams of code structure without running the app?

The best way to create Mermaid diagrams of code structure without running the app is to perform static analysis on compiled class output, generating class hierarchies, call graphs, and control-flow diagrams.

Do I need source code to generate control-flow graphs and package graphs?

No, you do not need source code to generate control-flow graphs and package graphs; the analysis requires only access to the compiled class directories from your Android, Java, or Kotlin build output.

How does static analysis of compiled classes help understand inheritance and call paths?

Static analysis of compiled classes helps understand inheritance and call paths by extracting structural relationships and method invocations directly from the bytecode, producing clear visual diagrams for holistic review.

Does this static analysis approach work with both Java and Kotlin compiled output?

Yes, this static analysis approach works with Java and Kotlin compiled output, as well as Android projects, by deriving class hierarchies, call paths, and package structures directly from the compiled class directories.