analyze-repo

Organize local code repositories into modules and generate analysis manifests.

Updated May 21, 2026
One-click install
npx skills add https://github.com/mica-agent/mica-solar-system --skill analyze-repo-mica-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-repo
Source: https://github.com/mica-agent/mica-solar-system/tree/main/.qwen/skills/analyze-repo
Command: npx skills add https://github.com/mica-agent/mica-solar-system --skill analyze-repo-mica-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly understand what a repository does, how its code is organized, and where to look next so you can navigate or modify the system with confidence.

Core Features & Use Cases

  • Module-first repo mapping: Builds a structured plan by enumerating top-level files and grouping the codebase into candidate modules suitable for independent deep dives.
  • Orchestrated, phase-based analysis: Uses a controlled workflow that pauses before deep reads, then dispatches per-module analysis to subagents to avoid context overflow.
  • Actionable outputs for exploration: Produces an analysis manifest and stores detailed module write-ups under .mica/repo-analysis/<repo>/ for later reference.

Quick Start

Ask your agent to analyze the repository at a local path, using the analyze-repo skill first, and then proceed through the confirmed module plan.

Frequently Asked Questions about analyze-repo

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

FAQPage Schema
How do I map a codebase architecture fast when joining a new repository?

Codebase analysis for architecture discovery works by enumerating top-level repository files and grouping source directories into candidate modules. A phased workflow then delegates per-module analysis to subagents with bounded file scope to prevent context overflow.

What is the best way to analyze a large local code repository without hitting context limits?

To analyze a large local code repository without hitting context limits, use an orchestrated workflow that writes a manifest with module sizing and budgets, then delegates per-module analysis to subagents with bounded file scope to prevent context overflow.

Can I use agent orchestration to break down a GitHub repository into independent modules?

Yes, agent orchestration can break down a GitHub repository into independent modules. The workflow enumerates top-level files, writes a manifest with module sizing and budgets, and delegates per-module analysis to subagents for systematic investigation.

How do I discover the build system and entry points of an unfamiliar local code repository?

You can discover the build system and likely entry points of a local code repository by running a structured analysis. The process organizes repository files, identifies languages, and maps source directories to help you navigate or modify the system.

Does codebase analysis work with any local repository path or do I need specific dependencies?

Codebase analysis works with a local repository path and requires no specific dependencies. It applies to tasks like orientation and architectural discovery, mapping source directories into independent modules for systematic investigation.

Why does my repository mapping workflow lose context when analyzing multiple modules?

Repository mapping workflows lose context when analyzing multiple modules due to context overflow. To avoid this, the workflow pauses before deep reads and delegates per-module analysis to subagents with bounded file scope, keeping the context manageable.