@spardutti/claude-skills 2.19.0 → 2.19.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/lib/setup-hook.mjs +10 -1
  2. package/package.json +1 -1
@@ -810,7 +810,16 @@ for owner in $OWNERS; do
810
810
  TOOL="stryker"
811
811
  # From inside the owning package: npx resolves against ITS node_modules, and
812
812
  # stryker.config.json lives there too. A monorepo root usually has neither.
813
- CMD="\${RUN}npx --no-install stryker run --incremental --force $FLAGS"
813
+ #
814
+ # Deliberately NOT --incremental. --force does rerun every mutant in scope,
815
+ # so the diff itself was always judged fresh — but incremental mode still
816
+ # merges reports/stryker-incremental.json into the REPORT for everything
817
+ # out of scope, and this gate greps the whole report. Survivors recorded
818
+ # months ago came back as findings against a diff that never touched them:
819
+ # 8 of them on one commit, all long since killed. --mutate already scopes
820
+ # the run to the changed hunks, so incremental buys nothing here and costs
821
+ # a cache that goes stale exactly the way mutmut's did.
822
+ CMD="\${RUN}npx --no-install stryker run $FLAGS"
814
823
  elif [ -f "$base"package.json ]; then
815
824
  MISSING="$MISSING $label needs Stryker:
816
825
  npm --prefix \${owner} i -D @stryker-mutator/core @stryker-mutator/vitest-runner
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@spardutti/claude-skills",
3
- "version": "2.19.0",
3
+ "version": "2.19.1",
4
4
  "description": "CLI to install Claude Code skills from the claude-skills collection",
5
5
  "type": "module",
6
6
  "repository": {