stack-detection

Identify repository technology stacks by analyzing configuration and manifest files.

Updated Mar 11, 2026

Search Tags:#developer tools #stack detection #technology identification #manifest files #configuration analysis #repository profiling

Ready to run

npx skills add https://github.com/Oiranca/copilot-agents-skills --skill stack-detection-oiranca

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stack-detection
Source: https://github.com/Oiranca/copilot-agents-skills/tree/main/skills/stack-detection
Command: npx skills add https://github.com/Oiranca/copilot-agents-skills --skill stack-detection-oiranca

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the identification of a software project's technology stack by analyzing configuration and manifest files, providing a structured overview without reading source code.

Core Features & Use Cases

Comprehensive Stack Profiling: Identifies languages, frameworks, runtimes, package managers, bundlers, and deployment indicators.
Evidence-Based Detection: Relies solely on configuration and manifest files for accurate detection.
Use Case: Quickly understand the technology landscape of a new or existing project by generating a STACK_PROFILE.md file.

Quick Start

Use the stack-detection skill to identify the technology stack of the current repository.

Frequently Asked Questions about stack-detection

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

FAQPage Schema

How do I identify the technology stack of a repository?▼

To identify the technology stack of a repository, analyze configuration and manifest files like package.json, tsconfig.json, and Dockerfile. This detects languages, frameworks, runtimes, package managers, bundlers, and deployment signals without reading source code.

Can I detect a project's framework and runtime by reading only configuration files?▼

Yes, you can detect a project's framework and runtime by reading configuration files. Analyzing manifests like package.json and tsconfig.json provides evidence-based identification of languages, frameworks, and deployment indicators without needing to parse source code.

What is the best way to profile a repository's tech stack without reading source code?▼

The best way to profile a repository's tech stack without source code is analyzing configuration and manifest files. This approach detects languages, runtimes, bundlers, package managers, and cloud deployment signals to generate a structured overview like STACK_PROFILE.md.

How do I generate a stack profile for a new software project?▼

You generate a stack profile for a new software project by analyzing its manifest and configuration files. Detecting signals from files like Dockerfile and cloud provider configurations produces a structured overview of the project's technology landscape.

Does stack detection work by analyzing cloud provider configurations and Dockerfiles?▼

Yes, stack detection works by analyzing cloud provider configurations and Dockerfiles. Reading these specific manifest files identifies deployment indicators, runtimes, and frameworks, providing an accurate, evidence-based overview of the repository's technology stack.

What manifest files are needed to detect a repository's package manager and bundler?▼

Manifest files like package.json and tsconfig.json are needed to detect a repository's package manager and bundler. Analyzing these configuration files accurately identifies the technology stack, including languages, frameworks, and deployment signals.