repo-detector

Extract repository characteristics into a standardized sheet from manifest files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ebijun1007/vibe-coding --skill repo-detector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-detector
Source: https://github.com/ebijun1007/vibe-coding/tree/main/.claude/skills/repo-detector
Command: npx skills add https://github.com/ebijun1007/vibe-coding --skill repo-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract repository characteristics (languages, frameworks, test runners, directory conventions, DI approaches, and key entry points) and summarize them into a single, reusable sheet to expedite planning.

Core Features & Use Cases

  • Centralized metadata extraction: Automatically collects language usage, framework signals, and project structure into a standardized sheet.
  • Pre-planning enabler: Provides planners with a consistent input to avoid re-surveying repositories during planning.
  • Use Case: Before planning a multi-repo rollout, generate a repository characteristics sheet to compare tech stacks and entry points at a glance.

Quick Start

Run the repo-detector plan-review preprocessor to generate the repository characteristics sheet.

Frequently Asked Questions about repo-detector

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

FAQPage Schema
How do I extract repository characteristics like languages and frameworks into a single sheet?

To extract repository characteristics into a single sheet, read manifest files like package.json, go.mod, or pyproject.toml to collect language usage, framework signals, and directory layout into a standardized, reproducible overview for planning.

What is the best way to survey project structure and entry points before planning a multi-repo rollout?

Surveying project structure and entry points before a multi-repo rollout is best done by generating a standardized repository characteristics sheet, which consolidates tech stacks and directory conventions into a single comparable view.

Can I detect frameworks and test runners across different repositories automatically?

Yes, you can detect frameworks and test runners across repositories automatically by analyzing manifest-like files and the directory layout, which identifies project characteristics and consolidates them into a reusable sheet.

Does repository metadata extraction support projects using Python, Go, and Node.js?

Repository metadata extraction supports projects using Python, Go, and Node.js by reading their respective manifest files such as pyproject.toml, go.mod, and package.json to identify languages, frameworks, and entry points.

When do I need a repository characteristics sheet for plan review?

You need a repository characteristics sheet for plan review during pre-planning tasks, providing planners with an up-to-date overview of project structure, language usage, and frameworks to avoid re-surveying repositories.

How do I consolidate directory conventions and DI approaches from multiple codebases?

To consolidate directory conventions and DI approaches from multiple codebases, analyze the directory layout and manifest files to extract project characteristics, outputting them into a standardized sheet for comparison.