mcp-geo-repo-extent-complexity

Analyze git repositories for extent and functional complexity across scopes.

3|1|Updated Jan 19, 2026

Search Tags:#git #analysis #metrics #complexity #hotspots #repo #extent

Ready to run

npx skills add https://github.com/chris-page-gov/mcp-geo --skill mcp-geo-repo-extent-complexity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcp-geo-repo-extent-complexity
Source: https://github.com/chris-page-gov/mcp-geo/tree/main/skills/mcp-geo-repo-extent-complexity
Command: npx skills add https://github.com/chris-page-gov/mcp-geo --skill mcp-geo-repo-extent-complexity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Analyze a git repository to quantify its extent and functional complexity across git_tracked and workspace scopes.

Core Features & Use Cases

Dual-scope inventory: git_tracked vs workspace to separate committed vs untracked/unignored content.
Complexity & hotspots: compute functional complexity and identify hotspots by complexity x churn.
Exclusions: honor generated/vendored content and optional Linguist attributes; supports optional GitHub stats.

Quick Start

Run the run_report.sh script from the repository root to generate the latest repo extent and complexity reports.

Frequently Asked Questions about mcp-geo-repo-extent-complexity

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

FAQPage Schema

How do I analyze a git repository for complexity and hotspots?▼

To analyze a git repository for complexity and hotspots, run the report script from the repository root to quantify functional extent and identify high-churn, high-complexity code areas across git_tracked and workspace scopes.

What is the difference between git_tracked and workspace scopes in repo analysis?▼

Git_tracked scope covers committed content, while workspace scope includes untracked and unignored files, allowing you to separate committed code from local changes during repository extent and complexity audits.

Does the repository complexity analysis exclude generated and vendored content?▼

Yes, the repository complexity analysis excludes generated and vendored content by default, ensuring that functional complexity metrics and hotspot calculations reflect only your actual source code.

Can I output git repository metrics to Markdown and JSON formats?▼

Yes, you can output git repository metrics to Markdown, JSON, and a manager report format, enabling automated governance reporting and local repository audit documentation.

What's the best way to identify code hotspots by churn and complexity?▼

The best way to identify code hotspots by churn and complexity is to run a repository analysis that cross-references git history metrics with functional complexity calculations, applying optional lookback windows for precise risk assessment.

Does the repository extent analysis support optional GitHub statistics?▼

Yes, the repository extent analysis supports optional GitHub statistics, allowing you to augment local git metrics with remote repository data for comprehensive governance reporting.