project-discovery

Scan repository structure and generate a discovery artifact of languages, frameworks, and tooling.

198|19|Updated May 7, 2026
One-click install
npx skills add https://github.com/testdouble/han --skill project-discovery-testdouble
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-discovery
Source: https://github.com/testdouble/han/tree/main/han-core/skills/project-discovery
Command: npx skills add https://github.com/testdouble/han --skill project-discovery-testdouble

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Project Discovery skill helps engineers gain a clear, up-to-date view of a repository's structure, tech stack, documentation layout, and infrastructure by automatically scanning and summarizing languages, frameworks, tooling, and configuration.

Core Features & Use Cases

  • Detect repository structure and project boundaries.
  • Identify languages, frameworks, dependencies, and tooling.
  • Produce a reusable discovery artifact for other skills or automation.

Quick Start

Run the discovery workflow to generate a structured report of the repository's languages, tooling, and project boundaries.

Frequently Asked Questions about project-discovery

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

FAQPage Schema
How do I automatically map repository structure and identify project boundaries?

Automatically mapping repository structure requires scanning dependency manifests, ADRs, and configuration files to capture a discovery artifact outlining per-project attributes and repository-wide infrastructure.

What is codebase discovery and how does it detect languages and tooling?

Codebase discovery is the automated process of scanning a repository to identify its languages, frameworks, dependencies, and tooling, summarizing the tech stack into a reusable structured artifact.

Can I use automated discovery to outline attributes in multi-project repositories?

Yes, you can use automated discovery to outline attributes in multi-project repositories by analyzing dependency manifests and configuration files to determine distinct project boundaries and toolchains.

How do I generate a discovery artifact for repository-wide documentation and infrastructure?

To generate a discovery artifact for repository-wide documentation and infrastructure, run an automated discovery workflow that scans configuration files and toolchains to summarize the overall repository layout.

What files are required to determine project boundaries and toolchains during repository analysis?

Determining project boundaries and toolchains during repository analysis requires access to dependency manifests, Architecture Decision Records (ADRs), and configuration files to accurately map the codebase.

Is manual codebase scanning better than automated discovery for identifying frameworks?

Automated discovery is generally better than manual codebase scanning for identifying frameworks because it automatically extracts languages, tooling, and configuration to produce a reusable, up-to-date discovery artifact.