investigation

Analyze codebases and infrastructure to surface decisions and dependencies.

3|1|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/metraton/gaia --skill investigation-metraton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigation
Source: https://github.com/metraton/gaia/tree/main/skills/investigation
Command: npx skills add https://github.com/metraton/gaia --skill investigation-metraton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigations establish context, constraints, and unknowns before proposing changes, reducing risk and rework.

Core Features & Use Cases

  • Anchored Context Extraction: Identify injected project context such as paths, services, and IDs to guide analysis.
  • Adjacent Resource Review: Inspect neighboring files to infer conventions, dependencies, and patterns.
  • Findings Synthesis: Produce concise, grounded findings that inform proposals and risk assessment.

Quick Start

Identify injected project context, examine 2-3 nearby resources, and extract unanswered questions to frame your investigation.

Frequently Asked Questions about investigation

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

FAQPage Schema
How do I analyze a codebase to surface dependencies before proposing changes?

To analyze a codebase, identify injected project context like paths and service IDs, inspect neighboring files to infer conventions, and synthesize concise findings to inform your change proposals and reduce rework.

What is the best way to assess infrastructure risk during early project discovery?

Assess infrastructure risk by applying early discovery techniques that extract anchored context and review adjacent resources, producing structured findings that highlight constraints and unknowns without altering live systems.

How do I extract unanswered questions and context from a codebase investigation?

Extract context from a codebase investigation by identifying injected project context, examining two to three nearby resources to infer patterns, and framing your unanswered questions to guide the findings synthesis.

Can I use this approach to investigate infrastructure without altering live systems?

Yes, you can investigate infrastructure without altering live systems by synthesizing context and reading adjacent resources to produce structured findings, ensuring your risk assessment remains strictly read-only.

What limitations exist when reviewing adjacent resources for risk assessment?

When reviewing adjacent resources for risk assessment, the limitation is that you must infer conventions and dependencies from only a few neighboring files, requiring careful synthesis to avoid incomplete context extraction.

Why does my codebase analysis miss constraints when proposing changes?

Your codebase analysis may miss constraints if it skips early discovery steps like anchored context extraction and adjacent resource review, leading to ungrounded change proposals and increased project risk.