@spardutti/claude-skills 2.19.0 → 2.19.2

package/lib/local.mjs

@@ -3,6 +3,10 @@
 // publishing it first.
 import { readdir, readFile } from "node:fs/promises";
 import { join } from "node:path";
+import { execFile } from "node:child_process";
+import { promisify } from "node:util";
+
+const exec = promisify(execFile);
 
 function parseFrontmatter(content, fallbackName) {
   const match = content.match(/^---\s*\n([\s\S]*?)\n---/);
@@ -25,6 +29,28 @@ async function listDir(dir) {
   try { return await readdir(dir, { withFileTypes: true }); } catch { return []; }
 }
 
+// Build output is not a project. Next.js writes a package.json into .next/,
+// .next/dev/ and .next/standalone/, so a scan that skipped only a hardcoded
+// list reported three phantom projects on a plain Next app — and then filtered
+// the real repo root out as "a root that delegates to a workspace". A second
+// list of build dirs drifts from .gitignore the moment a framework adds one, so
+// ask git the way ship-gate.sh already does. --directory collapses a fully
+// ignored tree to its own name, which is what keeps this output small.
+async function gitIgnoredDirs(projectDir) {
+  try {
+    const { stdout } = await exec(
+      "git",
+      ["-C", projectDir, "ls-files", "--others", "--ignored", "--exclude-standard", "--directory"],
+      { maxBuffer: 10 * 1024 * 1024 },
+    );
+    return new Set(
+      stdout.split("\n").filter((l) => l.endsWith("/")).map((l) => l.slice(0, -1)),
+    );
+  } catch {
+    return new Set();
+  }
+}
+
 export function makeLocalSource(root) {
   return {
     async fetchSkills() {
@@ -113,6 +139,8 @@ export async function reportToolNeeds(projectDir) {
   // needs a tool. A root that delegates is not the place to install, even once
   // the workspace it delegates to is already set up.
   const nested = { Stryker: false, mutmut: false };
+  // Empty outside a git repo, so the hardcoded list below still carries those.
+  const ignored = await gitIgnoredDirs(projectDir);
 
   async function scan(rel, depth) {
     if (depth > 2) return;
@@ -159,7 +187,9 @@ export async function reportToolNeeds(projectDir) {
     for (const e of entries) {
       if (!e.isDirectory()) continue;
       if (["node_modules", ".git", "dist", "build", ".venv", "venv", ".claude"].includes(e.name)) continue;
-      await scan(rel ? `${rel}/${e.name}` : e.name, depth + 1);
+      const child = rel ? `${rel}/${e.name}` : e.name;
+      if (ignored.has(child)) continue;
+      await scan(child, depth + 1);
     }
   }
 

package/lib/setup-hook.mjs

@@ -810,7 +810,16 @@ for owner in $OWNERS; do
     TOOL="stryker"
     # From inside the owning package: npx resolves against ITS node_modules, and
     # stryker.config.json lives there too. A monorepo root usually has neither.
-    CMD="\${RUN}npx --no-install stryker run --incremental --force $FLAGS"
+    #
+    # Deliberately NOT --incremental. --force does rerun every mutant in scope,
+    # so the diff itself was always judged fresh — but incremental mode still
+    # merges reports/stryker-incremental.json into the REPORT for everything
+    # out of scope, and this gate greps the whole report. Survivors recorded
+    # months ago came back as findings against a diff that never touched them:
+    # 8 of them on one commit, all long since killed. --mutate already scopes
+    # the run to the changed hunks, so incremental buys nothing here and costs
+    # a cache that goes stale exactly the way mutmut's did.
+    CMD="\${RUN}npx --no-install stryker run $FLAGS"
   elif [ -f "$base"package.json ]; then
     MISSING="$MISSING  $label needs Stryker:
       npm --prefix \${owner} i -D @stryker-mutator/core @stryker-mutator/vitest-runner

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spardutti/claude-skills",
-  "version": "2.19.0",
+  "version": "2.19.2",
   "description": "CLI to install Claude Code skills from the claude-skills collection",
   "type": "module",
   "repository": {