superpowers-mcp 6.3.7 → 6.3.9

package/skills/systematic-debugging/find-polluter.ps1

@@ -1,17 +1,19 @@
 #!/usr/bin/env pwsh
 # Bisection script to find which test creates unwanted files/state.
-# Usage: ./find-polluter.ps1 <file_or_dir_to_check> <test_pattern>
+# Usage: ./find-polluter.ps1 <file_or_dir_to_check> <test_pattern> <test command and arguments>
 
 $ErrorActionPreference = "Stop"
 
-if ($args.Count -ne 2) {
-    Write-Output "Usage: ./find-polluter.ps1 <file_to_check> <test_pattern>"
-    Write-Output "Example: ./find-polluter.ps1 '.git' 'src/**/*.test.ts'"
+if ($args.Count -lt 3) {
+    Write-Output "Usage: ./find-polluter.ps1 <file_to_check> <test_pattern> <test command and arguments>"
+    Write-Output "Example: ./find-polluter.ps1 '.git' 'src/**/*.test.ts' npx vitest run"
     exit 1
 }
 
 $pollutionCheck = $args[0]
 $testPattern = $args[1]
+$testCommand = $args[2]
+$testCommandArgs = if ($args.Count -gt 3) { @($args[3..($args.Count - 1)]) } else { @() }
 
 Write-Output "Searching for test that creates: $pollutionCheck"
 Write-Output "Test pattern: $testPattern"
@@ -53,7 +55,7 @@ foreach ($testFile in $testFiles) {
     }
 
     Write-Output "[$count/$total] Testing: $($testFile.FullName)"
-    & npm test $testFile.FullName *> $null
+    & $testCommand @testCommandArgs $testFile.FullName *> $null
 
     if (Test-Path -LiteralPath $pollutionCheck) {
         Write-Output ""

package/skills/systematic-debugging/find-polluter.sh

@@ -1,18 +1,19 @@
 #!/usr/bin/env bash
 # Bisection script to find which test creates unwanted files/state
-# Usage: ./find-polluter.sh <file_or_dir_to_check> <test_pattern>
-# Example: ./find-polluter.sh '.git' 'src/**/*.test.ts'
+# Usage: ./find-polluter.sh <file_or_dir_to_check> <test_pattern> <test command ...>
+# Example: ./find-polluter.sh '.git' 'src/**/*.test.ts' npx vitest run
 
 set -e
 
-if [ $# -ne 2 ]; then
-  echo "Usage: $0 <file_to_check> <test_pattern>"
-  echo "Example: $0 '.git' 'src/**/*.test.ts'"
+if [ $# -lt 3 ]; then
+  echo "Usage: $0 <file_to_check> <test_pattern> <test command ...>"
+  echo "Example: $0 '.git' 'src/**/*.test.ts' npx vitest run"
   exit 1
 fi
 
 POLLUTION_CHECK="$1"
 TEST_PATTERN="$2"
+TEST_COMMAND=("${@:3}")
 
 echo "🔍 Searching for test that creates: $POLLUTION_CHECK"
 echo "Test pattern: $TEST_PATTERN"
@@ -24,7 +25,7 @@ TEST_PATTERN="${TEST_PATTERN#./}"
 # find -path can't match '**/' against zero directory levels, so a pattern
 # like src/**/*.test.ts would skip src/top.test.ts; also try the pattern
 # with '**/' collapsed to cover files directly under the base directory.
-TEST_FILES=$(find . \( -path "./$TEST_PATTERN" -o -path "./${TEST_PATTERN//\*\*\//}" \) | sort -u)
+TEST_FILES=$(find . \( -path "./$TEST_PATTERN" -o -path "./${TEST_PATTERN//\*\*\//}" \) -print | sort -u)
 if [ -z "$TEST_FILES" ]; then
   TOTAL=0
 else
@@ -35,7 +36,8 @@ echo "Found $TOTAL test files"
 echo ""
 
 COUNT=0
-for TEST_FILE in $TEST_FILES; do
+while IFS= read -r TEST_FILE; do
+  [ -n "$TEST_FILE" ] || continue
   COUNT=$((COUNT + 1))
 
   # Skip if pollution already exists
@@ -48,7 +50,7 @@ for TEST_FILE in $TEST_FILES; do
   echo "[$COUNT/$TOTAL] Testing: $TEST_FILE"
 
   # Run the test
-  npm test "$TEST_FILE" > /dev/null 2>&1 || true
+  "${TEST_COMMAND[@]}" "$TEST_FILE" > /dev/null 2>&1 || true
 
   # Check if pollution appeared
   if [ -e "$POLLUTION_CHECK" ]; then
@@ -65,7 +67,7 @@ for TEST_FILE in $TEST_FILES; do
     echo "  cat $TEST_FILE         # Review test code"
     exit 1
   fi
-done
+done <<< "$TEST_FILES"
 
 echo ""
 echo "✅ No polluter found - all tests clean!"

package/skills/systematic-debugging/root-cause-tracing.md

@@ -101,10 +101,10 @@ If something appears during tests but you don't know which test:
 Use the bisection script `find-polluter.sh` in this directory:
 
 ```bash
-./find-polluter.sh '.git' 'src/**/*.test.ts'
+./find-polluter.sh '.git' 'src/**/*.test.ts' npx vitest run
 
 # Windows PowerShell:
-./find-polluter.ps1 '.git' 'src/**/*.test.ts'
+./find-polluter.ps1 '.git' 'src/**/*.test.ts' npx vitest run
 ```
 
 Runs tests one-by-one, stops at first polluter. See script for usage.

package/skills/using-superpowers/SKILL.md

@@ -32,7 +32,7 @@ When multiple skills apply, process skills come first — they set the approach,
 
 ## Skill Compositions & Pipelines
 
-Complex engineering workflows chain multiple skills end-to-end (see `docs/skill-compositions.md`):
+Complex engineering workflows chain multiple skills end-to-end. The complete published guide is available from the MCP resource `guide://superpowers/skill-compositions`:
 
 - **Feature Pipeline:** `brainstorming` → `writing-plans` → `using-git-worktrees` → `subagent-driven-development` (with `test-driven-development`) → `verification-before-completion` → `requesting-code-review` → `finishing-a-development-branch`
 - **Troubleshooting Pipeline:** `systematic-debugging` → `using-git-worktrees` → `dispatching-parallel-agents` → `test-driven-development` → `verification-before-completion` → `requesting-code-review`