hs:techstack

Detect a repository's languages, test commands, package managers, and CI systems.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/Dozyboy/VSF --skill hs-techstack-dozyboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hs:techstack
Source: https://github.com/Dozyboy/VSF/tree/main/Day2_VSF/Demo1/harness/plugins/hs/skills/techstack
Command: npx skills add https://github.com/Dozyboy/VSF --skill hs-techstack-dozyboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a verification harness is installed into a repository, it assumes pytest by default, which breaks on Node, Go, Rust, or Java projects. This Skill inspects the target repo and reports its real tech stack so test and setup commands match the actual toolchain instead of guessing. ## Core Features & Use Cases - Stack Detection: Identifies Python, JavaScript/TypeScript, Go, Rust, and Java from marker files like pyproject.toml, package.json, go.mod, Cargo.toml, and pom.xml. - Command Inference: Reads lockfiles and scripts.test to propose the correct test command and package manager (pnpm, yarn, uv, poetry, cargo, maven, and more). - CI Detection: Reports GitHub Actions, GitLab CI, or CircleCI when a workflow file is present. - Use Case: After installing the harness into a TypeScript monorepo, run detection to learn the repo uses pnpm with a declared test script, then hand that profile to hs:setup so hs:test runs pnpm test instead of pytest. ## Quick Start Ask the assistant to detect the tech stack of the target repository by running the detect_techstack.py script with the repo root and show the resulting JSON profile.

Frequently Asked Questions about hs:techstack

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

FAQPage Schema
How do I detect the tech stack of a repository automatically?▼

Run the detect_techstack.py script with the --root flag pointing at the repository. It scans for marker files like package.json, go.mod, and pyproject.toml, then emits a JSON profile listing each stack, its test command, package manager, and any CI system.

What languages and package managers does tech stack detection support?▼

It detects Python, JavaScript, TypeScript, Go, Rust, and Java. Package managers are inferred from lockfiles: pnpm, yarn, bun, or npm for JavaScript; poetry, uv, pipenv, or pip for Python; plus go, cargo, maven, and gradle.

Does the detection script modify or install anything in my repo?▼

No. The detector is strictly read-only. It never writes config, installs dependencies, or runs the detected test command. Applying changes based on the profile is handled separately by the hs:setup skill.

Why does the detected test command show null for my Node project?▼

A null test_cmd means the package.json declares no scripts.test entry. This is intentional honesty rather than an error; the detector reports only what the repo actually declares instead of guessing a runner.

What happens if the repository root is missing or unreadable?▼

The detector fails soft and returns an empty profile with no stacks instead of raising an error. This ensures the detection step cannot crash the host harness or block the surrounding workflow.