@spardutti/claude-skills 2.23.0 → 2.25.0

package/README.md

@@ -101,8 +101,7 @@ Portable slash commands installed to `.claude/commands/`. Some orchestrate paral
 | Command | What it does |
 |---------|--------------|
 | `/ship` | Unified delivery pipeline — commit → gate → PR → merge → release. The gate is the one enforcement moment: it checks the diff's file lengths, audits it against the skills installed in the project, and mutation-tests the changed lines to prove the tests would catch a break — **fixing what it finds** rather than handing you a list. It runs before the **PR**, not before every commit: its scope is the whole branch, so gating each commit re-mutated every file the branch had ever touched. `--force` skips it. No argument steps through interactively; `/ship pr` runs through PR creation; `/ship release` runs the full pipeline |
-| `/discover` | Find the right problem before deciding what to build — diverges first: generates competing framings through blind subagents under forced constraints, stress-tests the winner with a blind critic, and refuses to converge until every open question is answered or deferred. Run before `/preplan` |
-| `/preplan` | Resolve a fuzzy feature idea into concrete decisions — 6 fixed phases, one question at a time, ends with a decision log. Run before `/plan-feature` |
+| `/discover` | Find the right problem before deciding what to build — diverges first: generates competing framings through blind subagents under forced constraints, stress-tests the winner with a blind critic, and refuses to converge until every open question is answered or deferred, then drafts scope, non-goals, edge cases and success criteria for you to correct. Run before `/plan-feature` |
 | `/plan-feature` | Integration-first feature planning — 3 parallel subagents scan for reusable code, patterns, and touch points before producing a short plan |
 | `/refactor` | Detect size / complexity / duplication / coupling issues via 4 parallel subagents, then refactor |
 | `/deep-review` | Multi-agent deep code review — 5 parallel subagents catch guard bypasses, lost async state, wrong-table queries, dead references, protocol violations |

package/lib/scaffold-stryker.mjs

@@ -14,36 +14,31 @@
 import { readFile, writeFile, access } from "node:fs/promises";
 import { join } from "node:path";
 
+// ignoreStatic is the whole reason a first run is survivable. A string in a
+// module-level array or object is a static mutant, evaluated once at file load,
+// and Stryker's docs say testing one "often requires running all tests". A table
+// of 11 headings and 16 term rows produced 57 survivors and a gate that timed
+// out past 600s; with this set the same gate ran in 1m33s and the survivors were
+// gone without a single test written for them. It requires perTest coverage
+// analysis, which is why the two belong together.
+//
+// A shipped attempt to solve this in the ignorer — skip string mutants inside a
+// module-level array or object literal — was exactly the definition of a static
+// mutant, so it did the same job worse. It is gone; this option replaces it.
 const CONFIG = {
   $schema: "./node_modules/@stryker-mutator/core/schema/stryker-schema.json",
   testRunner: "vitest",
   plugins: ["@stryker-mutator/vitest-runner", "./stryker-classname-ignorer.mjs"],
   ignorers: ["tailwind-classnames"],
   coverageAnalysis: "perTest",
+  ignoreStatic: true,
   tempDirName: ".stryker-tmp",
 };
 
 // Bumped whenever IGNORER changes. A project scaffolded before a rule existed
 // has no other way to learn about it, and the file is generated, not authored —
 // so a missing marker means overwrite, not keep.
-const IGNORER_VERSION = "v2";
-
-// Exported and then serialised into the generated ignorer below, rather than
-// written twice. A copy in the template and a copy under test would agree with
-// each other and disagree with the shipped file.
-export function inDataTable(path) {
-  let found = false;
-  for (let p = path; p; p = p.parentPath) {
-    if (p.isFunction()) return false;
-    if (!found && p.isVariableDeclarator()) {
-      const init = p.node.init;
-      if (!init) return false;
-      if (init.type !== "ArrayExpression" && init.type !== "ObjectExpression") return false;
-      found = true;
-    }
-  }
-  return found;
-}
+const IGNORER_VERSION = "v3";
 
 // .mjs, not .js: an app without "type": "module" in its package.json cannot
 // load ESM from a .js file, and the plugin is ESM.
@@ -53,19 +48,10 @@ const IGNORER = `// Generated by @spardutti/claude-skills — ignorer ${IGNORER_
 // Ignore by WHERE the mutant sits, not by what kind it is. Disabling the
 // StringLiteral mutator globally would also stop mutating labels, keys and
 // separators — strings whose value is behaviour.
-import { PluginKind, declareValuePlugin } from "@stryker-mutator/api/plugin";
-
-// A string in a module-level array or object literal is copy: a heading, a
-// label, a term row. Mutating it produces 'Pizzas' -> 'Stryker was here!',
-// which can only be killed by asserting the table against a copy of itself —
-// the tautology the testing skill exists to stop. One table of 11 headings and
-// 16 rows produced 57 such survivors and a fifteen-minute gate.
 //
-// Any function between the string and the top disqualifies it: that is code
-// building a value, not a table of content. A non-string mutant in the same
-// table is left alone, because a number or a flag in a config object is
-// behaviour even when it sits in data.
-${inDataTable.toString()}
+// Content in a module-level table is NOT handled here. Those are static mutants,
+// and \`ignoreStatic\` in stryker.config.json covers them for less.
+import { PluginKind, declareValuePlugin } from "@stryker-mutator/api/plugin";
 
 export const strykerPlugins = [
   declareValuePlugin(PluginKind.Ignore, "tailwind-classnames", {
@@ -74,8 +60,6 @@ export const strykerPlugins = [
         return "styling, not behaviour";
       if (path.find((p) => p.isCallExpression() && p.node.callee.name === "cn"))
         return "styling, not behaviour";
-      if (path.isStringLiteral() && inDataTable(path))
-        return "copy in a data table, not behaviour";
     },
   }),
 ];
@@ -128,13 +112,31 @@ export async function scaffoldStryker(projectDir, rel) {
     }
     if (cfg === null) {
       unreadable.push(`${at}stryker.config.json`);
-    } else if ((cfg.ignorers ?? []).includes("tailwind-classnames")) {
-      kept.push(`${at}stryker.config.json`);
     } else {
-      cfg.plugins = [...new Set([...(cfg.plugins ?? []), "./stryker-classname-ignorer.mjs"])];
-      cfg.ignorers = [...new Set([...(cfg.ignorers ?? []), "tailwind-classnames"])];
-      await writeFile(configPath, JSON.stringify(cfg, null, 2) + "\n");
-      patched.push(`${at}stryker.config.json`);
+      const needsIgnorer = !(cfg.ignorers ?? []).includes("tailwind-classnames");
+
+      // ignoreStatic is only correct under perTest coverage analysis. Absent, we
+      // set both. Already perTest, we add the flag. Anything else was a
+      // deliberate choice and stays — silently switching it would change which
+      // mutants the project reports, which is not ours to decide.
+      const coverage = cfg.coverageAnalysis;
+      const canSetStatic = coverage === undefined || coverage === "perTest";
+      const needsStatic = cfg.ignoreStatic !== true && canSetStatic;
+
+      if (!needsIgnorer && !needsStatic) {
+        kept.push(`${at}stryker.config.json`);
+      } else {
+        if (needsIgnorer) {
+          cfg.plugins = [...new Set([...(cfg.plugins ?? []), "./stryker-classname-ignorer.mjs"])];
+          cfg.ignorers = [...new Set([...(cfg.ignorers ?? []), "tailwind-classnames"])];
+        }
+        if (needsStatic) {
+          cfg.coverageAnalysis = "perTest";
+          cfg.ignoreStatic = true;
+        }
+        await writeFile(configPath, JSON.stringify(cfg, null, 2) + "\n");
+        patched.push(`${at}stryker.config.json`);
+      }
     }
   } else {
     await writeFile(configPath, JSON.stringify(CONFIG, null, 2) + "\n");

package/lib/setup-hook.mjs

@@ -663,6 +663,13 @@ GAUNTLET_MUTATE=""
 GAUNTLET_SOURCE_EXT="ts|tsx|js|jsx|mjs|cjs|py|go|rs|java|kt|rb|php|c|h|cpp|hpp|cs|swift|gd"
 GAUNTLET_IGNORE_EXT="md|mdx|txt|rst|adoc|json|ya?ml|toml|lock|cfg|ini|env|csv|tsv|sql|html|css|scss|svg|png|jpg|jpeg|gif|webp|ico|pdf|woff2?|ttf|otf|mp3|mp4|wav|zip|gz|tres|tscn|import|godot"
 GAUNTLET_IGNORE_FILES="*.gen.ts *.gen.tsx *.generated.* */migrations/*.py */alembic/versions/*.py */components/ui/*.tsx */*.config.*"
+# Length-checked and skill-audited like everything else, but not mutated.
+# Mutation pays on logic and burns time on presentation: a component's mutants
+# are class names, copy and JSX shape, none of which is behaviour, and one
+# session spent an evening killing them. Logic that lives inside a component is
+# logic that wants extracting — which the 200-line rule already pushes toward.
+# Override in .claude/gauntlet.conf to mutate components too.
+GAUNTLET_NO_MUTATE='\\.(tsx|jsx)$'
 [ -n "\${HOME:-}" ] && [ -f "$HOME/.claude/gauntlet.conf" ] && . "$HOME/.claude/gauntlet.conf"
 [ -f ".claude/gauntlet.conf" ] && . ".claude/gauntlet.conf"
 
@@ -825,7 +832,7 @@ for owner in $OWNERS; do
   [ "$owner" = "." ] && label="<repo root>" || label="$owner/"
   OWNED=$(while IFS= read -r f; do
             [ "$(owner_of "$f")" = "$owner" ] && printf '%s\\n' "$f"
-          done <<< "$FILES")
+          done <<< "$FILES" | grep -vE "$GAUNTLET_NO_MUTATE" || true)
   [ -z "$OWNED" ] && continue
 
   # ONE comma-joined --mutate value, never a flag per range. Stryker's CLI

package/package.json

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