library-detection

Detect technologies by analyzing package manifests like package.json, pyproject.toml, go.mod, Cargo.toml, pubspec.yaml, and CMakeLists.txt. The library-detection skill parses these files to identify languages, frameworks, test tools, and build tools, producing a structured stack summary for immediate insight into project dependencies.

Yes. By running library-detection on your repository, you automatically generate a machine-readable stack report from manifests. This profile identifies all key technologies and outputs structured data suitable for configuring CI/CD pipelines, IDE settings, and documentation without manual investigation.

The tool analyzes package.json (Node.js), pyproject.toml (Python), go.mod (Go), Cargo.toml (Rust), pubspec.yaml (Dart), and CMakeLists.txt (C/C++) to extract language, framework, test, and build tool information. It relies on dependency patterns to map findings to actionable technology categories.

Library-detection produces machine-readable stack summaries that downstream tooling consumes to auto-configure CI/CD pipelines and IDE environments. By detecting languages and frameworks upfront, you eliminate manual setup and ensure configuration matches actual project dependencies.

The skill analyzes common manifests across multiple languages and frameworks in a single scan. It detects all present technologies—multiple languages, frameworks, and tools—in one pass, making it suitable for diverse and polyglot project structures.

Library-detection outputs a structured, machine-readable stack payload designed for downstream automation. The payload categorizes detected technologies by type—languages, frameworks, test tools, build tools—enabling programmatic integration into onboarding workflows and tooling pipelines.