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.