skills.rest
wfukatsu
wfukatsuCOMMUNITY
Explore all skills by this author →
GitHub

system-investigation

Analyze codebase tech stack, module layout, and debt hotspots for refactoring.

5|Updated Feb 10, 2026
Search Tags:#architecture#codebase#ddd#reporting#refactor#investigate#stack
One-click install
npx skills add https://github.com/wfukatsu/architecture-redesign-agent --skill system-investigation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: system-investigation
Source: https://github.com/wfukatsu/architecture-redesign-agent/tree/main/.claude/skills/system-investigation
Command: npx skills add https://github.com/wfukatsu/architecture-redesign-agent --skill system-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze a codebase to extract its structure, tech stack, potential issues, and DDD readiness to guide refactoring.

Core Features & Use Cases

  • Tech stack discovery and directory structure analysis for a given project.
  • Issue detection and technical debt assessment to prioritize refactors.
  • DDD readiness evaluation to plan modularization and domain boundaries, with actionable insights.

Quick Start

Provide the target project path and desired output location to begin the investigation.

Frequently Asked Questions about system-investigation

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

FAQPage Schema
What is the best way to analyze a legacy codebase for a refactor?▼

Analyzing a legacy codebase for a refactor involves mapping the directory structure, identifying the tech stack, and assessing technical debt hotspots. This investigation process extracts module layouts and evaluates DDD readiness to produce actionable architectural insights.

How do I evaluate DDD readiness in a multi-language repository?▼

Evaluating DDD readiness in a multi-language repository requires analyzing the directory structure and module layout to identify domain boundaries. By assessing technical debt hotspots and tech stack dependencies, you can plan modularization to support domain-driven design.

Can I detect technical debt hotspots by providing a project path?▼

Yes, providing a target project path allows the investigation tool to scan the codebase and detect technical debt hotspots. It analyzes the module structure and tech stack, generating detailed reports under the specified output directory to help prioritize refactoring efforts.

Does this codebase investigation tool work with modern multi-language tech stacks?▼

Yes, the codebase investigation tool is designed for both legacy and modern multi-language repositories. It discovers the tech stack, analyzes the directory structure, and evaluates DDD readiness, producing comprehensive reports to guide refactoring across diverse technology environments.

How to plan refactoring using tech stack discovery and directory analysis?▼

Plan refactoring by running tech stack discovery and directory structure analysis on your target project path. The investigation identifies issues, assesses technical debt, and evaluates DDD readiness, generating reports that provide actionable insights to guide the refactor.

Related Skills

Explore More Software Engineering Skills→
jinglemansweepjinglemansweep

jp-setup

Create a .plans directory with a .gitkeep file at the repository root.

Community
Basic
sumilee-pcusumilee-pcu

tech-debt

Scan source code for TODOs and complexity hotspots to manage technical debt.

Community
Intermediate
agony1997agony1997

explorer

Explore project structure with parallel sub-agents and generate PROJECT_MAP.md.

Community
Advanced
wfukatsuwfukatsu
12

investigate

Analyze technology stack, codebase structure, technical debt, and DDD readiness.

Community
Advanced