stack-detection

Detect project toolchains and CI/CD stacks from manifest files.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/breeze4/claude-config --skill stack-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stack-detection
Source: https://github.com/breeze4/claude-config/tree/main/skills/stack-detection
Command: npx skills add https://github.com/breeze4/claude-config --skill stack-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and reports the project toolchain and build/CI/CD stack, helping teams decide how to build, test, lint, and run code without manual auditing.

Core Features & Use Cases

  • Detects common stacks by scanning key files and manifests (package managers, build tools, and CI configurations).
  • Identifies languages, frameworks, and tooling to suggest appropriate commands for build, test, and quality checks.
  • Use Case: When starting a new project or auditing an existing repository to understand how to build, test, lint, and run it.

Quick Start

Run the stack-detection skill against a repository to surface the project's tooling and recommended commands

Frequently Asked Questions about stack-detection

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

FAQPage Schema
How do I detect the project toolchain and build stack of a repository?

To detect the project toolchain and build stack, you scan common manifest files like package.json, go.mod, and pyproject.toml alongside CI configurations to identify languages, package managers, and testing frameworks.

How does scanning manifest files identify CI/CD configurations and package managers?

Scanning manifest files identifies CI/CD configurations and package managers by locating and parsing standard build configs and dependency manifests, extracting the specific tooling and language stacks defined within them.

Can I use stack detection to find recommended commands for building and testing code?

Yes, you can use stack detection to find recommended commands. By identifying the project's languages, frameworks, and build tools, it suggests appropriate commands for building, testing, and linting the codebase.

What is the best way to audit an existing repository for language stacks and testing frameworks?

The best way to audit a repository for language stacks and testing frameworks is running an automated detection scan against the codebase to surface toolchains and CI/CD setups without manual file checking.

Does stack detection work with Go modules and Python pyproject.toml files?

Yes, stack detection works with Go modules and Python pyproject.toml files. It scans these standard manifests to determine the language stack, package manager, and build tooling used in the repository.

When do I need to scan for CI/CD configurations and build tools in a software project?

You need to scan for CI/CD configurations and build tools when starting a new project or auditing an existing repository, ensuring you understand how to properly build, test, lint, and run the code.