@spardutti/claude-skills 2.33.1 → 2.33.3

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, grounded clarifying questions follow, and on your go the same agent builds the plan and proves its tests with the ship gate |
+| `/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,15 @@ mutmut_unchecked() {  # mutmut_unchecked <label> <base> <count> <run log>
   echo "      it ahead of every host-local option."
 }
 
+# mutmut forks after importing the app, so code that only runs at import survives
+# every mutant. One agent baselined 39 of those as harmless.
+survivor_list() {  # survivor_list <survivors> <tool>
+  printf '%s\n' "$1" | sed 's/^/      /'
+  [ "$2" = mutmut ] || return 0
+  echo "      Only runs at import (app setup, router registration)? Then it is unreachable,"
+  echo "      not equivalent — see testing-best-practices/MUTATION-TESTING.md."
+}
+
 # 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>

package/hooks/ship-gate.sh

@@ -426,7 +426,7 @@ for owner in $OWNERS; do
 
   if [ -n "$SURVIVED" ]; then
     echo "  $label $TOOL — these lines can break and no test notices:"
-    printf '%s\n' "$SURVIVED" | sed 's/^/      /'
+    survivor_list "$SURVIVED" "$TOOL"
     if [ "$FOUND" -gt 20 ]; then
       echo "      ... $((FOUND - 20)) more not shown. Every file with findings:"
       if [ "$TOOL" = stryker ]; 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.1",
+  "version": "2.33.3",
   "description": "Guardrails for Claude Code — best-practice skills, planning commands, and delivery gates.",
   "type": "module",
   "repository": {