lnd-navigate

Locate entry points and subsystem boundaries in the lnd Go codebase.

57|18|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/lightninglabs/lightning-agent-tools --skill lnd-navigate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lnd-navigate
Source: https://github.com/lightninglabs/lightning-agent-tools/tree/main/skills/lnd-navigate
Command: npx skills add https://github.com/lightninglabs/lightning-agent-tools --skill lnd-navigate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly orient yourself inside the lnd Go codebase, so you can find the right files, follow subsystem boundaries, and understand how the daemon is wired together without scanning the entire repository.

Core Features & Use Cases

  • Entry Point Maps: Identifies the main startup files such as main.go, lnd.go, server.go, and rpcserver.go.
  • Subsystem Navigation: Points you to routing, HTLC switching, wallet, funding, gossip, watchtower, storage, and wire-protocol packages.
  • Workflow Tracing: Shows common paths like payment initiation, channel open and close, gossip ingestion, and breach handling.
  • Developer Efficiency: Includes grep patterns and interface tables to speed up debugging, code review, and implementation planning.

Quick Start

Ask the assistant to show where a specific lnd feature starts, how it flows through the codebase, and which files or interfaces implement it.

Frequently Asked Questions about lnd-navigate

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

FAQPage Schema
How do I navigate the lnd Go codebase to find payment routing logic?

To navigate the lnd codebase for payment routing, locate the main entry points and subsystem boundaries using maps of files like server.go and rpcserver.go. This identifies the specific packages handling HTLC switching and routing workflows.

What is the best way to trace an HTLC workflow through the lnd daemon?

Tracing an HTLC workflow through the lnd daemon involves following common code paths like payment initiation and channel management. You can use provided grep patterns and interface tables to speed up debugging and implementation tracing.

How do I find the entry points for lnd's gossip and channel management subsystems?

Finding the entry points for lnd's gossip and channel management subsystems requires locating the main startup files such as main.go and lnd.go. This maps the daemon's structure to point you directly to the relevant supporting packages.

Can I use this to locate RPC behavior implementation files in the lnd repository?

Yes, you can locate RPC behavior implementation files in the lnd repository by identifying the rpcserver.go entry point. This helps map the interface boundaries and grep-oriented discovery across the daemon's supporting packages.

Does this help with repository onboarding for debugging lnd's wire-protocol packages?

Yes, this assists with repository onboarding for debugging lnd's wire-protocol packages by orienting you inside the codebase. It shows subsystem boundaries and workflow tracing to help you understand how the daemon is wired together without scanning everything.