detect-stack-and-update-config

Detects project tech stack and tooling, then updates openspec/config.yaml with findings.

6|7|Updated Jun 4, 2026
One-click install
npx skills add https://github.com/nodesource/nsolid-plugin --skill detect-stack-and-update-config-nodesource
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: detect-stack-and-update-config
Source: https://github.com/nodesource/nsolid-plugin/tree/main/.opencode/skills/detect-stack-and-update-config
Command: npx skills add https://github.com/nodesource/nsolid-plugin --skill detect-stack-and-update-config-nodesource

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually keeping project configuration in sync with the actual tech stack is error-prone and often forgotten after tooling changes. This Skill inspects project files to detect the stack, test runner, linter, type checker, and build system, then writes the results into openspec/config.yaml automatically. ## Core Features & Use Cases - Stack Detection: Parses package.json, go.mod, Cargo.toml, pyproject.toml, CMakeLists.txt, tsconfig.json, and CI workflow files to identify languages, frameworks, and package managers. - Tooling Detection: Identifies test runners (vitest, jest, pytest, go test), coverage tools, linters (eslint, biome, ruff, clippy), type checkers (typescript, mypy), and formatters (prettier, black, rustfmt). - Safe Config Updates: Updates only the context, testing, and quality sections of openspec/config.yaml while preserving all other YAML structure and custom schemas. - Use Case: After running an init command or migrating a project from jest to vitest, run this Skill to refresh the config so downstream workflows use the correct test and lint commands. ## Quick Start Detect the project stack and update openspec/config.yaml with the detected tooling and testing capabilities.

Frequently Asked Questions about detect-stack-and-update-config

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

FAQPage Schema
How do I detect a project's tech stack automatically?▼

Scan manifest files like package.json, go.mod, Cargo.toml, and pyproject.toml to identify the language and framework, then inspect scripts and config files for test runners, linters, and type checkers. This Skill performs that detection and records results in openspec/config.yaml.

How do I update openspec/config.yaml after changing test frameworks?▼

Run this Skill after switching tooling such as migrating from jest to vitest. It re-detects the test runner, coverage command, linter, and type checker, then updates only the context, testing, and quality sections of the config.

Which languages and project files does stack detection support?▼

Detection covers Node.js via package.json, Go via go.mod, Rust via Cargo.toml, Python via pyproject.toml, C/C++ via CMakeLists.txt, TypeScript via tsconfig.json, and CI commands via GitHub Actions workflow files.

Will updating the config overwrite my existing YAML settings?▼

No. The Skill preserves all existing YAML structure and rules, modifying only the context, testing, and quality sections. It respects custom schemas such as schema: ns-workflow and validates the output as valid YAML before writing.

What happens if a tool cannot be detected in the project?▼

Undetectable items are reported as "not detected" in the risks output rather than guessed. The Skill returns a summary listing detected stack, testing capabilities, quality tools, and which config sections changed.