Claude GitHub Copilot Skill

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 tech

LLM Mart · 0 points · 2 views 0 listing impressions 0 install-command copies
Download drvoss-everything-copilot-cli-plugins_copilot-native-workflows_skills_stack-detector-1ca2355.zip · 2 KB

Install

skills CLI npx skills add https://github.com/drvoss/everything-copilot-cli/tree/main/plugins/copilot-native-workflows/skills/stack-detector
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install drvoss-everything-copilot-cli@llmmart
Git git clone https://github.com/drvoss/everything-copilot-cli.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole drvoss/everything-copilot-cli collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

No shell access? In tools that deny shell commands by default (for example headless agy -p or Cursor --mode=ask), skip the PowerShell snippets below. List the project root with your file-listing tool and read package.json, lockfiles, and config files directly; the detection rules and the recommendation table apply unchanged.

1. Detect Runtime & Package Manager

# 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

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

$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

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
Files (everything-copilot-cli)
  • SKILL.md 8 KB
    ---
    name: stack-detector
    license: MIT
    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
    
    > **No shell access?** In tools that deny shell commands by default (for example headless
    > `agy -p` or Cursor `--mode=ask`), skip the PowerShell snippets below. List the project root with
    > your file-listing tool and read `package.json`, lockfiles, and config files directly; the
    > detection rules and the recommendation table apply unchanged.
    
    ### 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
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.