repo-scanning

Analyze repositories to detect languages, frameworks, structure, domains, and health.

95|4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/aspenkit/aspens --skill repo-scanning-aspenkit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-scanning
Source: https://github.com/aspenkit/aspens/tree/main/.agents/skills/repo-scanning
Command: npx skills add https://github.com/aspenkit/aspens --skill repo-scanning-aspenkit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deterministic repository analysis surfaces languages, frameworks, structure, domains, entry points, size, and health to help teams understand codebases quickly without guesswork.

Core Features & Use Cases

  • Deterministic detection of languages and frameworks based on repo contents (beyond simple file extensions).
  • Domain discovery, source-root mapping, and import-graph integration to reveal architecture and dependencies.
  • Health checks and size estimation to identify hotspots, risks, and maintenance needs.
  • Structured, display-ready data suitable for dashboards, audits, and project planning.

Quick Start

Run the repo-scanning skill on a repository to generate a structured profile including languages, frameworks, structure, domains, entry points, size, and health.

Frequently Asked Questions about repo-scanning

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

FAQPage Schema
How do I identify languages and frameworks in a repository automatically?

Repository scanning detects languages and frameworks deterministically by analyzing repo contents beyond simple file extensions, providing structured data on the codebase's technology stack and architecture.

What is deterministic codebase analysis and when do I need it?

Deterministic codebase analysis reliably surfaces languages, frameworks, structure, domains, and health metrics without guesswork, needed when teams require consistent, structured outputs for dashboards or audits.

How do I map out a repository's domains and entry points?

Mapping repository domains and entry points involves analyzing source roots and performing domain discovery to reveal architecture and dependencies, generating an import-graph integration profile.

Can I run health checks and size estimation on diverse codebases?

Health checks and size estimation work on diverse codebases to identify hotspots, risks, and maintenance needs, producing display-ready data suitable for project planning and audits.

What is the best way to generate structured data for codebase architecture understanding?

Generating structured data for codebase architecture requires deterministic detection of structure and domains, producing export-ready graph data that supports scalable codebase understanding and dashboards.

Does repository scanning work for diverse codebases without specific dependencies?

Repository scanning works on diverse codebases with no external dependencies, using deterministic detection to identify frameworks, structure, and health metrics for scalable codebase understanding.