investigation

Investigate codebases with parallel agents and generate Obsidian documents with DataviewJS indexes.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/baphled/dotopencode --skill investigation-baphled
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigation
Source: https://github.com/baphled/dotopencode/tree/main/skills/investigation
Command: npx skills add https://github.com/baphled/dotopencode --skill investigation-baphled

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of deeply investigating and documenting codebases, transforming complex findings into structured, navigable Obsidian notes with auto-generated indexes.

Core Features & Use Cases

  • Parallel Agent Exploration: Utilizes multiple agents to concurrently analyze different aspects of a codebase (structure, architecture, debt, testing, CI/CD, documentation).
  • Structured Documentation: Synthesizes findings into a standardized set of Markdown documents within an Obsidian vault.
  • Auto-Generated Indexes: Creates DataviewJS-powered indexes for easy discovery and navigation of investigation findings.
  • Use Case: When onboarding to a new, large project, use this Skill to get a comprehensive, documented overview of its architecture, technical debt, and testing strategy within minutes.

Quick Start

Use the investigation skill to explore the codebase at /path/to/project and generate a structured report in your Obsidian vault.

Frequently Asked Questions about investigation

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

FAQPage Schema
How do I conduct a systematic codebase investigation and document the architecture?

A systematic codebase investigation uses parallel agent exploration to concurrently analyze architecture, technical debt, and testing, synthesizing findings into structured Markdown documents for reproducible records.

What is the best way to audit technical debt across a large codebase?

Auditing technical debt is best handled by deploying parallel agents to assess different codebase aspects concurrently, which then generates structured documentation detailing the debt findings.

How do I auto-generate indexes for codebase investigation notes in Obsidian?

Auto-generating indexes for codebase investigation notes in Obsidian utilizes DataviewJS to create searchable, auto-generated indexes that allow easy discovery and navigation of findings.

Does the codebase investigation process support onboarding to new projects?

Yes, the codebase investigation process supports onboarding to new projects by providing a comprehensive, documented overview of the application's structure, architecture, and testing strategy within minutes.

Can I use parallel agents to assess CI/CD and documentation during a code audit?

Yes, you can use parallel agents to concurrently assess CI/CD, documentation, and codebase structure during a code audit, ensuring all aspects are explored simultaneously for a comprehensive report.