tech-stack-detection

Detects a project's tech stack, package manager, and key configurations from its files and directory structure.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/I2olanD/dotfiles --skill tech-stack-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-stack-detection
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/tech-stack-detection
Command: npx skills add https://github.com/I2olanD/dotfiles --skill tech-stack-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the detection of a project's tech stack, packaging, and tooling by analyzing root artifacts, manifests, and directory structure.

Core Features & Use Cases

  • Package Manager Detection: Reads lock files (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb) to identify the primary ecosystem.
  • Framework & Tooling Signatures: Inspects manifest files (package.json, pyproject.toml, Cargo.toml) and framework-specific configs to classify frameworks.
  • Architecture & Directory Patterns: Detects common patterns like app/ or src/, routes/, pages/ to infer framework usage and project type.
  • Use Case: Starting work on unfamiliar repositories to guide setup, tooling choices, and recommendations.

Quick Start

Run the tech-stack-detection skill on a project root to identify its tech stack, package manager, and key configuration patterns. For example, analyze a repository with package.json and next.config.js to confirm Next.js + npm/yarn usage.

Frequently Asked Questions about tech-stack-detection

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

FAQPage Schema
How do I detect the tech stack and framework of an unfamiliar codebase?

You can detect a project's tech stack by analyzing root artifacts, lock files, and manifest files like package.json or pyproject.toml. This identifies the framework, package manager, and key configurations to guide setup and tooling choices for unfamiliar repositories.

What is the best way to identify a package manager from lock files?

Identifying a package manager involves reading lock files such as package-lock.json, yarn.lock, pnpm-lock.yaml, or bun.lockb. This reveals the primary ecosystem and confirms the exact tooling required to manage project dependencies.

Can I use directory patterns to infer framework usage in a project?

Yes, you can infer framework usage by detecting common directory patterns like app/, src/, routes/, or pages/. Analyzing these structural signatures alongside manifest files helps classify the framework and determine the project type.

Does tech stack detection work with Python, Rust, and Go projects?

Tech stack detection works across Node.js, Python, Rust, Go, Ruby, and PHP projects. It inspects ecosystem-specific manifests like Cargo.toml and pyproject.toml to output the detected framework, package manager, and recommended commands.

How do I find recommended commands for an unfamiliar repository?

Finding recommended commands involves analyzing project manifests and framework indicators like next.config.js. The detection process outputs key configs and suggested commands tailored to the recognized package manager and tech stack.