repo-analyzer

Analyze code repositories to create structured profiles mapping dependencies, APIs, and module structure.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Doxee-Product-Development/requirements-automation --skill repo-analyzer-doxee-product-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-analyzer
Source: https://github.com/Doxee-Product-Development/requirements-automation/tree/main/.claude/skills/repo-analyzer
Command: npx skills add https://github.com/Doxee-Product-Development/requirements-automation --skill repo-analyzer-doxee-product-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Quickly turning scattered repository information into a structured, navigable profile by performing tree-first discovery, selective reads, and tiered analysis, so teams can understand codebases without scanning everything.

Core Features & Use Cases

  • Progressive disclosure pipeline that starts with a lightweight tree scan and gradually reads high-signal files to derive dependencies, build systems, and module structure.
  • LOCAL mode for analyzing a locally cloned repo and API mode for remote Bitbucket repos, including monorepo detection and per-module profiling.
  • Outputs include a consolidated repo profile with module-level sections, data-flow diagrams, and feature catalogs for easy mapping and decisions.
  • Use case: when given a large monorepo, generate an actionable map of modules, dependencies, and potential integration points to inform architecture decisions.

Quick Start

Use this skill to generate a repo profile for a given Bitbucket workspace and repository slug, selecting a tier and mode to control depth and cost.

Frequently Asked Questions about repo-analyzer

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

FAQPage Schema
How do I generate a structured profile of a large monorepo without scanning every file?

To analyze a large monorepo efficiently, use a progressive-disclosure pipeline that starts with a lightweight tree scan and gradually reads high-signal files to map dependencies and module structure.

What is progressive-disclosure repo analysis and how does it map codebase dependencies?

Progressive-disclosure repo analysis is a staged, query-driven workflow that performs tree-first discovery and selective file reads to derive dependencies, build systems, and module structure for scalable insight.

Can I analyze remote Bitbucket repositories to map module structure and APIs?

Yes, you can analyze remote Bitbucket repositories using API mode, which connects via the Bitbucket API to detect monorepos and generate per-module profiles, dependencies, and data-flow diagrams.

Does repo profiling support local codebases and generate per-module diagrams?

Repo profiling supports LOCAL mode for analyzing locally cloned codebases, outputting a consolidated repo profile with module-level sections, data-flow diagrams, and feature catalogs for easy mapping.

What is the best way to control analysis depth and cost when profiling large codebases?

The best way to control analysis depth and cost is by selecting a specific tier and mode during repo profiling, which scales the progressive-disclosure reads and cache management to match your requirements.

When should I use a staged, cache-enabled workflow for codebase mapping?

Use a staged, cache-enabled workflow for codebase mapping when dealing with large monorepos, ensuring efficient, scalable insight by avoiding full scans and relying on cached, tiered analysis outputs.