stack-detection

Stack detection examines file extensions and import statements in the files being changed first, then falls back to project root markers like pom.xml, go.mod, Cargo.toml, or package.json. The most specific signal available determines which stack skills to load.

Common markers include pom.xml or build.gradle for Java, go.mod for Go, Cargo.toml for Rust, pyproject.toml or requirements.txt for Python, and package.json for JavaScript. A package.json with a React dependency additionally signals the React stack.

Yes, mixed-stack tasks load all relevant stack skills simultaneously without conflict. For example, a Go backend with a React frontend loads both go-stack and react-stack, since each skill covers its own domain.

Run it at the start of any engineering task, before loading stack-specific skills. It should also always be paired with baseline skills like implementation-principles and testing-and-validation regardless of the detected stack.

File extensions alone can be ambiguous when a task touches generic or shared files, so detection falls back to project root build configuration. If neither signal is conclusive, the stack may need manual confirmation from the engineer.