@spardutti/claude-skills 2.33.0 → 2.33.2

package/README.md

@@ -133,7 +133,7 @@ Portable slash commands installed to `.claude/commands/`. Some orchestrate paral
 |---------|--------------|
 | `/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, then drafts scope, non-goals, edge cases and success criteria for you to correct. Run before `/plan-feature` |
-| `/plan-feature` | Integration-first feature planning, then building — 3 parallel subagents scan for reusable code, patterns and touch points, and the plan lands with a contract and a per-worker file split; on your go it dispatches parallel implementation workers that each load their own skills, then mutation-tests their work once and sends each test gap back to the worker that wrote it, and reports one diff |
+| `/plan-feature` | Integration-first feature planning, then building — 3 parallel subagents scan for reusable code, patterns and touch points, grounded clarifying questions follow, and on your go the same agent builds the 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 |
 | `/test-review` | Write-then-verify test review — scopes to the diff, runs red-green + mutation gates, then an isolated read-only subagent proves each test would catch a regression instead of rubber-stamping it |

package/hooks/ship-gate-projects.sh

@@ -52,6 +52,14 @@ mutmut_unchecked() {  # mutmut_unchecked <label> <base> <count> <run log>
   echo "      it ahead of every host-local option."
 }
 
+# A scoped --baseline replaces only the changed modules' names. Rebuilding the whole
+# file re-mutated an entire API to accept eleven of them.
+baseline_write() {  # baseline_write <baseline file> <survivors file> <scope regex, or empty>
+  if [ -z "$3" ]; then cp "$2" "$1"; return; fi
+  grep -vE "^($3)\.x" "$1" | cat - "$2" | sort -u > "$1.new"
+  mv "$1.new" "$1"
+}
+
 family_of() {  # js, py, or any when no manifest says
   o=$(owner_of "$1")
   if [ -f "$o/package.json" ]; then echo js

package/hooks/ship-gate.sh

@@ -291,15 +291,15 @@ for owner in $OWNERS; do
     continue
   elif [ -n "$(py_mutmut "$base")" ]; then
     TOOL="mutmut"
-    # 3.x has no per-line scoping, only fnmatch globs over mutant NAMES, so a
-    # compare run is scoped to the changed modules. A baseline is recorded whole.
+    # 3.x has no per-line scoping, only fnmatch globs over mutant NAMES, so once a
+    # baseline exists every run, --baseline included, is scoped to the changed modules.
     #
     # `mutmut run` prints 🙁 for a survivor and exits 0 either way — parsing it
     # reports clean with survivors sitting there, which is a false green and
     # worse than reporting nothing. `mutmut results` is the readable source:
     # it prints "<mutant name>: survived" per survivor.
     M="$(py_mutmut "$base")"
-    [ "$MODE" != baseline ] && [ -f "$base.mutmut-baseline" ] && MODS=$(printf '%s\n' "$OWNED" \
+    [ -f "$base.mutmut-baseline" ] && MODS=$(printf '%s\n' "$OWNED" \
       | sed -n "s#^$base\(.*\)\.py\$#\1#p" | tr / . | sed 's#^src\.##' | sort -u)
     [ -n "$MODS" ] && GLOBS=$(printf " '%s.x*'" $MODS) \
       && SCOPE_RE=$(printf '%s\n' "$MODS" | sed 's/\./\\./g' | paste -sd'|' -)
@@ -405,7 +405,7 @@ for owner in $OWNERS; do
     fi
 
     if [ "$MODE" = baseline ]; then
-      cp "$NOWF" "$BL"
+      baseline_write "$BL" "$NOWF" "$SCOPE_RE"
       NOTE="  $label mutmut — baseline set: $(wc -l < "$BL") survivor(s) accepted. Commit $BL."
       SURVIVED=""
     elif [ -f "$BL" ]; then

package/lib/setup-hook.mjs

@@ -127,7 +127,7 @@ export async function setupHook(targetDir = process.cwd()) {
   console.log(`  Hook installed: .claude/hooks/${AUTO_MARK_FILENAME}`);
   console.log(`  Hook installed: .claude/hooks/${APPLICATION_GATE_FILENAME}`);
   console.log(`  Hook installed: .claude/hooks/${GAUNTLET_FILENAME}`);
-  console.log(`  Installed: .claude/hooks/${SHIP_GATE_FILENAME} (used by /ship and /plan-feature)`);
+  console.log(`  Installed: .claude/hooks/${SHIP_GATE_FILENAME} (used by /ship)`);
   console.log(`  Hook installed: .claude/hooks/${SHIP_GATE_HOOK_FILENAME}`);
   console.log(`  Settings updated: .claude/settings.json`);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spardutti/claude-skills",
-  "version": "2.33.0",
+  "version": "2.33.2",
   "description": "Guardrails for Claude Code — best-practice skills, planning commands, and delivery gates.",
   "type": "module",
   "repository": {