stack-detector
/stack-detector
Use when starting work on an unfamiliar codebase or onboarding a contributor and you need to know which skills and rules from this collection apply — scans the project's tech stack (package.json, config files, lockfiles) and recommends the most relevant ones for the detected technologies.
- Author
- drvoss ↗
- Repository
- everything-copilot-cli ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when starting work on an unfamiliar codebase or onboarding a contributor and you need to know which skills and rules from this collection apply — scans the project's tech stack (package.json, config files, lockfiles) and recommends the most relevant ones for the detected technologies.
Original author description
Use when starting work on an unfamiliar codebase or onboarding a contributor and you need to know which skills and rules from this collection apply — scans the project's tech stack (package.json, config files, lockfiles) and recommends the most relevant ones for the detected technologies.
How it works
- Why This is Copilot-Exclusive
- When to Use
- Workflow
- Notes
SKILL.md preview
---
name: stack-detector
description: Use when starting work on an unfamiliar codebase or onboarding a contributor and you need to know which skills and rules from this collection apply — scans the project's tech stack (package.json, config files, lockfiles) and recommends the most relevant ones for the detected technologies.
metadata:
category: copilot-exclusive
copilot_feature: "File system inspection, git ls-files, package.json analysis"
---
# Stack Detector
## Why This is Copilot-Exclusive
This skill is specific to the **everything-copilot-cli collection**: the recommendation table
maps detected technologies to skill and rule file paths that only exist in this repository.
Other AI agents can also inspect file systems, but this skill's value is the curated mapping
to this specific collection's skills and rules — not the file-scanning mechanics itself.
## When to Use
- At the start of a session on an unfamiliar codebase, before or alongside `context-prime`
- When you want focused recommendations for which skills and rules apply to this project
(`context-prime` loads broad context; `stack-detector` targets specific recommendations)
- When onboarding a new contributor and recommending which skills to study
- When auditing a project to suggest missing tooling or practices
## Workflow
### 1. Detect Runtime & Package Manager
```powershell
# Check for Node.js project
if (Test-Path "package.json") {
$pkg = Get-Content "package.json" | ConvertFrom-Json
Write-Host "Node.js project detected"
Write-Host "Name: $($pkg.name)"
}
# Detect package manager from lockfile
$lockfiles = @{
"pnpm-lock.yaml" = "pnpm"
"yarn.lock" = "yarn"
"package-lock.json" = "npm"
"bun.lockb" = "bun"
}
foreach ($file in $lockfiles.Keys) {
if (Test-Path $file) { Write-Host "Package manager: $($lockfiles[$file])"; break }
}
# Python
if ((Test-Path "pyproject.toml") -or (Test-Path "requirements.txt")) {
Write-Host "Python project detected"
}
# Go
if (Test-Path "go.mod") { Write-Host "Go project detected" }
# Java / Kotlin
if ((Test-Path "build.gradle") -or (Test-Path "pom.xml")) {
Write-Host "JVM project detected"
}
```
### 2. Detect Frameworks & Libraries
```powershell
if (Test-Path "package.json") {
$pkg = Get-Content "package.json" | ConvertFrom-Json
$deps = @()
if ($pkg.dependencies) { $deps += $pkg.dependencies.PSObject.Properties.Name }
if ($pkg.devDependencies) { $deps += $pkg.devDependencies.PSObject.Properties.Name }
$frontendMap = @{
"next" = "Next.js"
"react" = "React"
"vue" = "Vue"
"nuxt" = "Nuxt"
"@angular" = "Angular"
"svelte" = "Svelte"
"astro" = "Astro"
}
foreach ($key in $frontendMap.Keys) {
if ($deps -match $key) { Write-Host "Framework: $($frontendMap[$key])" }
}
$backendMap = @{
"express" = "Express"
"@nestjs" = "NestJS"
"hono" = "Hono"
"fastify" = "Fastify"
}
foreach ($key in $backendMap.Keys) {
if ($deps -match $key) { Write-Host "Backend: $($backendMap[$key])" }
}
$dbMap = @{
"prisma" = "Prisma"
"drizzle" = "Drizzle ORM"
"@supabase" = "Supabase"
"typeorm" = "TypeORM"
}
foreach ($key in $dbMap.Keys) {
if ($deps -match $key) { Write-Host "Database/ORM: $($dbMap[$key])" }
}
$testingMap = @{
"vitest" = "Vitest"
"playwright" = "Playwright"
"jest" = "Jest"
"cypress" = "Cypress"
}
foreach ($key in $testingMap.Keys) {
if ($deps -match $key) { Write-Host "Testing: $($testingMap[$key])" }
}
$cloudMap = @{
"wrangler" = "Cloudflare Workers"
"vercel" = "Vercel"
"@aws-sdk" = "AWS SDK"
}
foreach ($key in $cloudMap.Keys) {
if ($deps -match $key) { Write-Host "Cloud: $($cloudMap[$key])" }
}
}
```
### 3. Detect Config Files
```powershell
$configMap = @{
"next.config.*" = "Next.js"
"vite.config.*" = "Vite"
"tailwind.config.*" = "Tailwind CSS"
"vitest.config.*" = "Vitest"
"playwright.config.*" = "Playwright"
"wrangler.toml" = "Cloudflare Workers"
"vercel.json" = "Vercel"
"astro.config.*" = "Astro"
"drizzle.config.*" = "Drizzle ORM"
"tsconfig.json" = "TypeScript"
}
foreach ($pattern in $configMap.Keys) {
if (Get-ChildItem -Filter $pattern -ErrorAction SilentlyContinue) {
Write-Host "Config detected: $($configMap[$pattern])"
}
}
```
### 4. Recommend Skills & Rules
Based on the detected stack, recommend the following from this repository:
| Detected Technology | Recommended Skills | Recommended Rules |
|----------------------|------------------------------------------|---------------------------------------------------------------------|
| TypeScript | `tdd-workflow`, `code-review` | `rules/languages/typescript.md` |
| Next.js | `commit-workflow`, `release` | `rules/frameworks/nextjs.md` |
| React | `code-review`, `refactor-clean` | `rules/frameworks/react.md` |
| Prisma / Drizzle | `evaluate-repository` | `rules/frameworks/prisma.md` |
| Playwright | `test-coverage`, `e2e-testing` | `rules/frameworks/playwright.md` |
| Vitest | `tdd-workflow`, `eval-harness` | `rules/frameworks/vitest.md` |
| NestJS / Express | `security-scan` | `rules/frameworks/nestjs.md` |
| Cloudflare Workers | `cost-audit` | `rules/frameworks/cloudflare-workers.md` |
| Python | `security-scan`, `evaluate-repository` | `rules/languages/python.md` |
| Go | `security-scan` | `rules/languages/golang.md` |
| Java / JVM | `security-scan`, `evaluate-repository` | `rules/languages/java.md` |
| Any project | `security-scan` | `rules/common/supply-chain-security.md` |
| Next.js + Prisma | `nextjs-prisma` | `rules/frameworks/nextjs.md`, `rules/frameworks/prisma.md` |
| React + Vitest | `react-vitest` | `rules/frameworks/react.md`, `rules/frameworks/vitest.md` |
| NestJS + Prisma | `nestjs-prisma` | `rules/frameworks/nestjs.md`, `rules/frameworks/prisma.md` |
> **Note**: See `README.md` for the current full list of available skills and rules.
### 5. Output Summary
```powershell
Write-Host ""
Write-Host "=== Stack Detection Complete ==="
Write-Host "Recommended skills for this project:"
Write-Host " /context-prime -- load live project context"
Write-Host " /commit-workflow -- if Git workflow needed"
Write-Host " /security-scan -- if security audit needed"
Write-Host "(Add detected framework-specific skills as available)"
```
## Notes
- This skill reads files only — it makes no changes to the project
- Combine with `context-prime` for a complete session initialization
- The recommendation table above is updated as new framework-specific rules and combo skills
are added in later phases of this repository's roadmap
Versions
The database has no other skills named stack-detector.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 70e877e647c2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100analyzing-projects
Analyzes codebases to understand structure, tech stack, patterns, and conventions. Use when onboarding to a new project, exploring unfamiliar code, or when asked "how does this work?" or "what's the architecture? - 100setup
Onboarding wizard: scans the codebase and stack, recommends skills and MCP servers, scores readiness. Use when setting up OrchestKit in a project or rescanning after big changes. - 90stack-detection
Establish what a frontend project actually uses — framework, router, package manager, styling, component layer, TypeScript posture — from package.json, lockfiles, config files and the source itself, before loading framework-specific guidance or writing a line of code. Fires at… - 100grill-recon
Use for initial codebase reconnaissance — quickly survey project structure, tech stack, config files, and existing documentation to establish context before deeper analysis. Always the first skill run during a grill review, and also useful standalone when orienting to an unfamiliar repository. - 100delivery-bootstrap
Use when starting implementation on a new or unfamiliar codebase. Auto-detects tech stack and sets up development context. - 90dev-repo-onboarding
Use to map an unfamiliar repo structure, entrypoints, tech stack, commands, tests, risks, and safe next steps.