codebase-analyzer

Analyze codebases to identify tech stack, architecture, and integration touchpoints.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/JuniYadi/claude-code --skill codebase-analyzer-juniyadi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-analyzer
Source: https://github.com/JuniYadi/claude-code/tree/main/super-dev/skills/codebase-analyzer
Command: npx skills add https://github.com/JuniYadi/claude-code --skill codebase-analyzer-juniyadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams and engineers understand an existing codebase by surfacing patterns, architecture, and tech stack to inform feature judgments.

Core Features & Use Cases

  • Tech Stack Discovery: Identify languages, frameworks, and key dependencies used in the repository.
  • Architecture & Patterns: Detect MVC, Clean Architecture, service layers, and modular structures to guide design decisions.
  • Integration Points & Risks: Enumerate potential integration touchpoints and areas likely affected by new features.
  • Use Case: Before proposing a feature, run this skill to understand where it fits and what changes are needed.

Quick Start

Scan your repository at the target path with the workingDirectory parameter to generate a structured context report.

Frequently Asked Questions about codebase-analyzer

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

FAQPage Schema
How do I analyze an existing codebase to understand its architecture and tech stack?

To analyze an existing codebase, scan the repository path to discover technologies from config files and map architectural patterns. This provides a structured context report detailing the tech stack, file structure, and integration touchpoints.

How do I detect integration touchpoints before proposing a new feature?

To detect integration touchpoints for a new feature, run a contextual codebase analysis. This surfaces existing service layers and modular structures, enumerating potential changes and highlighting areas likely affected by conflicts.

Can I identify architectural patterns like Clean Architecture across multi-language repositories?

Yes, you can identify architectural patterns across multi-language repositories. The analysis detects structures like MVC, Clean Architecture, and service layers by reading config files and mapping the file structure to guide design decisions.

What's the best way to map potential conflicts when adding features to a codebase?

The best way to map potential conflicts is by scanning the working directory to surface architectural context. This evaluates the existing tech stack and file structure, enumerating potential changes and integration risks before proposing features.

Does codebase analysis require specific dependencies to detect frameworks and languages?

No specific dependencies are required for codebase analysis. The tool identifies languages, frameworks, and key dependencies natively by detecting technologies directly from repository config files.

When should I not use automated codebase analysis for feature judgments?

Automated codebase analysis may be limited when evaluating highly abstract or undocumented architectural patterns. It should not replace human feature judgment, but rather surface tech stack context and integration touchpoints to inform decisions.