Run any Skill in Manus with one click

run-tests

Stars2

Forks1

UpdatedApril 10, 2026 at 17:57

This skill should be used when the user asks to "run tests", "run-tests", "test the patcher", "run swift tests", "check tests", "run unit tests", or "verify tests pass".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Soul-Craft

Soul-Craft/buddy-evolver

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	run-tests
description	This skill should be used when the user asks to "run tests", "run-tests", "test the patcher", "run swift tests", "check tests", "run unit tests", or "verify tests pass".
disable-model-invocation	true

Run Tests — Swift Test Suite

Run the BuddyPatcher Swift unit tests and report results.

Steps

1. Run tests

cd "${CLAUDE_PLUGIN_ROOT}/scripts/BuddyPatcher" && swift test 2>&1

2. Parse and report results

Read the output and extract:

Total tests run
Tests passed
Tests failed
Time elapsed

3. Display formatted report

Test Suite Report — 178 tests across 12 files
══════════════════════════════════════════════

  AnalyzeTests              ✅ / ❌
  ArgumentParsingTests      ✅ / ❌
  BackupRestoreTests         ✅ / ❌
  BinaryDiscoveryTests       ✅ / ❌
  ByteUtilsTests             ✅ / ❌
  MetadataTests              ✅ / ❌
  OrchestrationTests         ✅ / ❌
  PatchEngineTests           ✅ / ❌
  PatchLengthInvariantTests  ✅ / ❌
  RegressionTests            ✅ / ❌
  SoulPatcherTests           ✅ / ❌
  ValidationTests            ✅ / ❌
  VariableMapDetectionTests  ✅ / ❌

  Total: N tests, M passed, K failed (X.XXs)
  Result: ALL PASS ✅  /  FAILURES ❌

4. If failures

Show the specific test names and assertion messages that failed. Suggest checking the corresponding source files:

Analyze.swift — binary introspection (--analyze mode)
ArgumentParsing.swift — CLI argument handling
BackupRestore.swift — backup/restore and SHA-256 verification
BinaryDiscovery.swift — binary path resolution
ByteUtils.swift — byte pattern matching
Metadata.swift — patch metadata persistence
Orchestration.swift — patch pipeline coordination
PatchEngine.swift — binary patching functions
RegressionTests.swift — one test per previously-fixed bug
SoulPatcher.swift — companion config updates
Validation.swift — input validation (emoji, name, personality, binary path)
VariableMapDetection.swift — species variable maps

5. If build fails

If swift test fails during compilation (before running tests), report the build errors separately and suggest checking:

Package.swift for target configuration
Whether all source files are in the correct directories

More from this repository

same repository

audit-security

Soul-Craft/buddy-evolver

This skill should be used when the user asks to "security audit", "check security", "audit buddy", "check backup health", "verify backup", or "security check".

2026-04-162

clean-cache

Soul-Craft/buddy-evolver

This skill should be used when the user asks to "clean cache", "cache clean", "clear build cache", "free disk space", "clean up", "remove build artifacts", "clean .build", "manage cache", or "show cache size".

2026-04-162

review-token

Soul-Craft/buddy-evolver

This skill should be used when the user asks to "token review", "review tokens", "optimize tokens", "audit context size", "reduce token footprint", "session review", "end of session review", or "check token usage".

2026-04-162

session-review

Soul-Craft/buddy-evolver

Pre-commit pipeline for Buddy Evolver — runs token optimization, full test-all.sh, security review, docs sync, and comment audit. INVOKE IMMEDIATELY when the user says any variant of "session review", "review session", "session end", "end session", "end the session", "ending session", "session over", "session done", "wrap up", "wrapping up", "finish up", "finishing up", "done for now", "close out", "ready to commit", or "before commit" — treat these as direct invocations, not topics for discussion. Do NOT ask whether the timing is right, do NOT argue that a commit already happened (run anyway and report what's still actionable), do NOT defer. If the user actively says "don't run" or "skip", honor that — otherwise invoke now.

2026-04-162

sync-docs

Soul-Craft/buddy-evolver

This skill should be used when the user asks to "sync docs", "update docs", "sync documentation", "update readme", "update claude md", "docs out of date", "check documentation", or "fix docs".

2026-04-162

session-deploy

Soul-Craft/buddy-evolver

Use after a PR is merged to GitHub main. Syncs local main, verifies the merged code builds, removes merged worktrees, and stages the current worktree for automatic self-cleanup on /exit. With --release, also bumps version, updates CHANGELOG, tags the commit, pushes to trigger marketplace publish, and verifies the local plugin reloads. Use when the user says "deploy", "session deploy", "pr merged", "post-merge sync", "deploy session", "clean up after merge", or "release new version".

2026-04-162

Run Tests — Swift Test Suite

Run the BuddyPatcher Swift unit tests and report results.

Steps

1. Run tests

cd "${CLAUDE_PLUGIN_ROOT}/scripts/BuddyPatcher" && swift test 2>&1

2. Parse and report results

Read the output and extract:

Total tests run

Tests passed

Tests failed

Time elapsed

3. Display formatted report

Test Suite Report — 178 tests across 12 files ══════════════════════════════════════════════ AnalyzeTests ✅ / ❌ ArgumentParsingTests ✅ / ❌ BackupRestoreTests ✅ / ❌ BinaryDiscoveryTests ✅ / ❌ ByteUtilsTests ✅ / ❌ MetadataTests ✅ / ❌ OrchestrationTests ✅ / ❌ PatchEngineTests ✅ / ❌ PatchLengthInvariantTests ✅ / ❌ RegressionTests ✅ / ❌ SoulPatcherTests ✅ / ❌ ValidationTests ✅ / ❌ VariableMapDetectionTests ✅ / ❌ Total: N tests, M passed, K failed (X.XXs) Result: ALL PASS ✅ / FAILURES ❌

4. If failures

Show the specific test names and assertion messages that failed. Suggest checking the corresponding source files:

Analyze.swift — binary introspection (--analyze mode)

ArgumentParsing.swift — CLI argument handling

BackupRestore.swift — backup/restore and SHA-256 verification

BinaryDiscovery.swift — binary path resolution

ByteUtils.swift — byte pattern matching

Metadata.swift — patch metadata persistence

Orchestration.swift — patch pipeline coordination

PatchEngine.swift — binary patching functions

RegressionTests.swift — one test per previously-fixed bug

SoulPatcher.swift — companion config updates

Validation.swift — input validation (emoji, name, personality, binary path)

VariableMapDetection.swift — species variable maps

5. If build fails

If swift test fails during compilation (before running tests), report the build errors separately and suggest checking:

Package.swift for target configuration

Whether all source files are in the correct directories