investigation

Name: investigation
Availability: InStock
Author: nagasakah

Map codebase structure, dependencies, and risks into an investigation report.

Updated Feb 8, 2026

Search Tags:#documentation #investigation #codebase #dependencies #risk-analysis #report-generation

Ready to run

npx skills add https://github.com/NagasakaH/dev-process --skill investigation-nagasakah

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigation
Source: https://github.com/NagasakaH/dev-process/tree/main/.claude/skills/general-purpose/investigation
Command: npx skills add https://github.com/NagasakaH/dev-process --skill investigation-nagasakah

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps investigators quickly gather and organize information about a codebase, requirements, and risks before making changes.

Core Features & Use Cases

Identify project structure, key files, and dependencies to understand the codebase context.
Analyze existing implementation patterns and risk factors to inform safe changes.
Generate an investigation report and risk analysis artifacts for stakeholders (docs, templates, and diagrams).

Quick Start

Run an initial inquiry to map the repository structure, locate essential files (README.md, AGENTS.md, CLAUDE.md), identify dependencies, and generate an investigation report.

Frequently Asked Questions about investigation

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

FAQPage Schema

How do I investigate a codebase to map structure and dependencies before making changes?▼

To investigate a codebase, systematically scan the repository structure and key files like README.md to map dependencies and implementation patterns. This process generates an investigation report and risk analysis artifacts to inform safe code changes.

What is codebase risk analysis and when do I need it?▼

Codebase risk analysis is the process of identifying implementation patterns and potential risk factors in a repository. You need it before modifying software projects to ensure structured discovery, document existing dependencies, and generate artifacts that inform safe changes.

What's the best way to generate documentation for an unfamiliar software project?▼

The best way to generate documentation for an unfamiliar project is to run a structured discovery workflow that scans repository structure and key files like AGENTS.md. This produces comprehensive investigation reports that map dependencies and document codebase context.

Does codebase investigation work for software projects of any size?▼

Yes, codebase investigation applies to software projects of any size. The structured discovery workflow scales to map repository structures, locate essential files like CLAUDE.md, and identify dependencies regardless of the overall scale of the codebase.

How do I identify dependencies and implementation patterns in a repository?▼

To identify dependencies and implementation patterns, scan the repository structure and essential files such as README.md. This systematic investigation maps related patterns and dependencies, producing a risk analysis report for stakeholders.

What are the limitations of using a structured discovery workflow for codebase investigation?▼

The investigation workflow relies on scanning repository structures and key files like README.md, AGENTS.md, and CLAUDE.md. If these specific files are absent or lack documentation, the generated investigation report and risk analysis may have limited context.