repo-analyzer

Analyzes GitHub repository structure across five dimensions and writes standardized analysis documents.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/nickgogan/improvement-loop --skill repo-analyzer-nickgogan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-analyzer
Source: https://github.com/nickgogan/improvement-loop/tree/main/.claude/skills/repo-analyzer
Command: npx skills add https://github.com/nickgogan/improvement-loop --skill repo-analyzer-nickgogan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Evaluating external GitHub repositories for architectural patterns requires repetitive manual cloning, file counting, and context-file hunting. This Skill automates that structural survey so every watched library gets the same consistent, comparable analysis. ## Core Features & Use Cases - Five-Dimension Structural Analysis: Extracts structural inventory, context file maps, workflow topology, governance models, and cross-agent protocols from any cloned repo. - Version-Aware Re-Analysis: Compares the analyzed version against the watched-library registry and skips repos that are already up to date unless forced. - Standardized Output Docs: Writes analysis documents with a fixed frontmatter schema and section template to a central analysis directory, plus an index. - Use Case: After adding a new AI agent framework to your watched-libraries registry, run the analysis to map its CLAUDE.md files, agent definitions, and workflow phases, then compare it against previously analyzed repos. ## Quick Start Ask the assistant to run the repo-analyzer on a specific watched library by name, or on all registered libraries, optionally restricting it to specific dimensions.

Frequently Asked Questions about repo-analyzer

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

FAQPage Schema
How do I analyze the structure of a GitHub repository?▼

Invoke the skill with the library name from the watched-libraries registry, for example repo-analyzer gsd. It shallow-clones the repo to a gitignored cache, extracts patterns across five dimensions, and writes a standardized analysis document.

What dimensions does repository structural analysis cover?▼

The analysis covers five dimensions: structural inventory (file counts, markdown composition), context file map (CLAUDE.md, agent definitions), workflow topology (phases and gates), governance model (rules and constraints), and cross-agent protocol (handoffs and coordination).

Can I re-analyze a repo after a version bump?▼

Yes. The skill compares the analyzed_version in the existing analysis doc against the registry's last_evaluated_version and skips unchanged repos. Use the --force flag to re-analyze even when the version has not changed.

Does the analysis execute code from cloned repositories?▼

No. The skill is strictly read-only: it never runs npm install, pip install, make, or any scripts from cloned repos. It only inspects file structure, reads context files, and greps for patterns.

What happens if ast-grep is not installed?▼

The skill treats ast-grep as an optional dependency. It checks availability first and falls back to find-based file statistics, recording in the analysis doc whether the code outline pass ran or was skipped.

When should I not use repo structural analysis?▼

Do not use it to run or test external code, write research findings, or produce cross-repo comparisons. Cross-repo comparison was moved to the separate compare-repos skill, and research findings go through the research-loop workflow.