stack-detector

To detect the technology stack during project onboarding, the Skill scans package manifests like package.json, lockfiles, and config files with read-only access to identify runtimes, frameworks, databases, and cloud providers used in the codebase.

Yes, you can map detected frameworks and tools to specific Copilot skills and rules using predefined mapping tables that connect identified technologies to curated framework, language, and tooling guidance documents within the repository.

The best way to recommend framework-specific skills for a new codebase is to scan package manifests and config files to discover technologies, then map them to curated Copilot skills and rules using predefined tables for targeted guidance.

Stack detection does work with lockfiles and config files for security audits by requiring read-only access to source files to discover runtimes, package managers, databases, and cloud providers, helping auditors see available capabilities for the stack.

Technology mapping requires read-only access to source files because it needs to scan package manifests, lockfiles, and config files to discover runtimes, frameworks, and tools without modifying the repository during project initialization or audits.