Ada Support in Maguyva: Specs, Bodies, and Package Graphs

Why Ada repositories need a dependency map

Ada separates what a package promises (.ads) from how it does it (.adb). That is good engineering, and it also means a single change touches several files that a text search will not connect for you. Long-lived Ada systems add another layer: generics, tagged types, tasks, and protected objects whose relationships matter more than any one file.

Maguyva gives an agent that dependency map before it proposes an edit, which is the order high-integrity review expects.

What Maguyva extracts in Ada

Maguyva covers .ads, .adb, and .ada. Subprogram bodies and procedure and function specifications are extracted as callable symbols, so a routine’s spec and its body are both searchable. Symbol matching is case-insensitive, as Ada itself is.

Imports come from with and use clauses, with the keyword stripped so the graph stores the package name. The graph also records calls, inheritance and overrides on tagged types, instantiation, type references, reads and writes, and exception raise and handler edges.

In structural search, task types, protected types, record types, and interface types are selectable as type definitions, and entry bodies are selectable as methods.

Example agent prompts

• “Which units depend on Flight_Control.Sensors, and which of its subprograms do they call?” (dependency_search incoming)
• “Show the spec and body for Compute_Trajectory and every caller.” (find_symbol)
• “Explain how the telemetry task hands data to the logging protected object.” (get_task_context)

Known limits

• Ada uses the same syntax for some calls, record field access, and indexing. Maguyva filters built-in types, standard library packages, attribute functions, and operators (about 113 patterns) to keep the call graph clean, so calls into the standard library are not graph edges. Record-field access and indexing are told apart from calls by their position in the grammar, not by a list of field names. Common text I/O calls such as Put_Line, Put, and Get are kept on purpose.
• use clauses change visibility but are not selected as imports in structural search; with clauses are.
• Record and interface type nodes can be anonymous fragments, so name-based structural queries may miss them. Use find_symbol for named types.

Next steps

Connect a repository with the quickstart, then check the support matrix on the compatibility page. If your Ada code binds to C, read the C guide too.