investigate

Trace execution paths and verify integration points across service boundaries.

Updated Feb 25, 2026

Search Tags:#code review #code analysis #debugging #code exploration #execution tracing #service integration

Ready to run

npx skills add https://github.com/LayerDynamics/Lore --skill investigate-layerdynamics

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/LayerDynamics/Lore/tree/main/lore/skills/investigate
Command: npx skills add https://github.com/LayerDynamics/Lore --skill investigate-layerdynamics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a systematic approach to understanding complex codebases, tracing execution paths, and identifying integration points, reducing the time spent on code comprehension.

Core Features & Use Cases

Execution Path Tracing: Follows function calls and service interactions step-by-step.
Boundary Verification: Checks request/handler matching, error handling, and authentication at service boundaries.
Pattern Analysis: Compares code against established conventions to identify deviations.
Use Case: When encountering an unfamiliar service, use this Skill to trace how a specific request is handled from the entry point to the database or external service.

Quick Start

Use the investigate skill to trace the execution path for how the user service handles authentication.

Frequently Asked Questions about investigate

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

FAQPage Schema

How do I trace execution paths across multiple services to understand system architecture?▼

Tracing execution paths across services requires mapping function calls, data transformations, and boundary interactions. This Skill systematically traverses code step-by-step to trace requests from entry points to databases or external services.

What is the best way to prepare for a code review on an unfamiliar service?▼

Preparing for code reviews on unfamiliar services involves analyzing execution paths, verifying integration points, and checking error handling. This Skill compares code against established conventions to identify deviations before review.

How do I debug complex request flows by identifying cross-service boundaries?▼

Debugging complex flows requires verifying request and handler matching, authentication, and error handling at service boundaries. This Skill maps cross-service interactions by systematically analyzing function calls and data transformations.

Can I use this to analyze how authentication is handled from the entry point to the database?▼

Yes, you can analyze authentication handling by tracing execution paths from entry points through service boundaries. This Skill follows function calls and service interactions to verify integration points and data transformations.

When do I need systematic code traversal for understanding a codebase?▼

Systematic code traversal is needed when encountering unfamiliar services, debugging complex flows, or preparing for code reviews. It reduces code comprehension time by mapping execution paths and identifying integration points.

Does this approach work for checking service boundary error handling mechanisms?▼

Yes, boundary verification checks request and handler matching, authentication, and error handling at service boundaries. This Skill analyzes error handling mechanisms during systematic code traversal and execution path tracing.