interaction-mapper

Map CRD-controller relationships and cross-repo gRPC topology from code and proto definitions.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/COLDTURNIP/longhorn-workspace --skill interaction-mapper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interaction-mapper
Source: https://github.com/COLDTURNIP/longhorn-workspace/tree/main/.opencode/skills/interaction-mapper
Command: npx skills add https://github.com/COLDTURNIP/longhorn-workspace --skill interaction-mapper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, grep, sed, awk, find, mktemp, head.

What problem does it solve?

This Skill helps engineers understand how CRDs are reconciled by controllers and how gRPC services are wired across Longhorn repositories, enabling rapid impact analysis and smoother onboarding.

Core Features & Use Cases

  • CRD-Controller Mapping: Identify which controllers reconcile specific CRDs and surface the mapping to the responsible code paths.
  • gRPC Topology Discovery: Map cross-repo gRPC service definitions to their callers and implementations.
  • Architectural Onboarding: Provide a clear cross-repo call graph to new engineers iterating on the Longhorn architecture.

Quick Start

Run from workspace root: bash .opencode/skills/interaction-mapper/map_interactions.sh

Frequently Asked Questions about interaction-mapper

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

FAQPage Schema
How do I map CRD reconciliation paths to their controllers across repositories?

To map CRD reconciliation paths, this Skill parses code to identify which controllers reconcile specific CRDs and surfaces the responsible code paths. It traces CRD-controller relationships across Longhorn repositories using standard Unix tools.

What is the best way to discover cross-repo gRPC service topology in Longhorn?

Discovering cross-repo gRPC topology involves parsing proto definitions to map service callers and implementations. This Skill generates rpc-topology index files that provide a clear cross-repo call graph for architectural analysis.

Does this gRPC topology mapping tool require any special dependencies to run?

No special dependencies are required. The tool relies entirely on standard Unix tools already present in most environments, specifically git, grep, sed, awk, find, mktemp, and head to parse code and proto definitions.

How do I generate a cross-repo call graph for architectural onboarding?

You generate a cross-repo call graph by running the map_interactions.sh script from your workspace root. This produces index files for CRD-interaction and rpc-topology that visually map distributed components for new engineers.

Can I use standard Unix tools for impact analysis on distributed components?

Yes, you can use standard Unix tools for impact analysis on distributed components. The solution uses git, grep, sed, and awk to trace CRD reconciliation and gRPC call flows, supporting rapid impact analysis across multiple repositories.