deep-research

Analyze a codebase to produce structured findings with file references and risks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mojwang/macbook-dev-setup --skill deep-research-mojwang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-research
Source: https://github.com/mojwang/macbook-dev-setup/tree/main/.claude/skills/deep-research
Command: npx skills add https://github.com/mojwang/macbook-dev-setup --skill deep-research-mojwang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebase research is tedious and error-prone; this Skill automates thorough analysis to produce repeatable, structured findings with references, dependencies, patterns, and risk signals.

Core Features & Use Cases

  • Automated file-path mapping and reference discovery to delineate module boundaries and architecture.
  • Dependency and pattern discovery across the repository to reveal coupling and common design patterns.
  • Structured reporting that maps Current State, Patterns Found, Dependencies, Risks, and Open Questions for onboarding and due-diligence.

Quick Start

Analyze the repository to generate a structured findings report detailing file references, dependencies, patterns, and risks.

Frequently Asked Questions about deep-research

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

FAQPage Schema
How do I analyze a codebase to find dependencies and architectural patterns?▼

Analyzing a codebase to find dependencies and patterns is done by mapping file references and searching text to compile a structured report. This process reveals module boundaries, coupling, and common design patterns for onboarding and due diligence.

What is the best way to generate a structured risk assessment for a complex repository?▼

Generating a structured risk assessment for a complex repository involves using an explorer agent with text search tools to map the current state. It highlights potential risks, dependencies, and open questions to guide remediation planning.

Can I use standard text search tools to map module boundaries in a large codebase?▼

Standard text search tools like Glob and Grep can map module boundaries in a large codebase. They discover file paths and references to delineate architecture, revealing how different parts of the repository couple and interact.

How do I automate codebase research to produce repeatable findings for due diligence?▼

Automating codebase research for repeatable findings uses a forked explorer agent to scan the repository. It produces a structured report covering current state, dependencies, risks, and open questions, reducing manual error during due diligence.

Does automated codebase analysis work for understanding architecture in complex repositories?▼

Automated codebase analysis works for understanding architecture in complex repositories by delineating module boundaries and discovering patterns. It compiles file references and dependency mappings into a structured findings report suitable for planning.

What should be included in a codebase analysis report to ensure thorough onboarding?▼

A thorough codebase analysis report for onboarding should include the current state, patterns found, dependencies, risks, and open questions. Mapping these elements provides a clear architectural overview and highlights potential areas needing remediation.