Menu
Run SUnit tests in the running Pharo image. Use when verifying changes after import, or when checking results for a specific test class or package.
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.
Based on SOC occupation classification
Import Tonel package into running Pharo image. Use when loading edited .st files into Pharo after code changes.
Comprehensive Pharo Smalltalk development workflow guide with AI-driven Tonel editing. Provides expertise in Tonel file format syntax (class definitions with name, superclass, instVars, category, method categories, class comment placement), package structure (package.st placement, directory organization, BaselineOf dependencies), development workflow (Edit → Import → Test cycle with absolute paths, re-import timing, test execution), and Pharo best practices (CRC format documentation, method categorization conventions). Use when working with Pharo Smalltalk projects, creating or editing Tonel .st files, organizing packages and dependencies, resolving import order issues, writing class comments, implementing standard Pharo development patterns (Singleton, Settings, etc.), or troubleshooting Tonel syntax.
Systematic debugging guide for Pharo Smalltalk development. Provides expertise in error diagnosis (MessageNotUnderstood, KeyNotFound, SubscriptOutOfBounds, AssertionFailure), incremental code execution with eval tool, intermediate value inspection, error handling patterns (`on:do:` blocks), stack trace analysis, UI debugger window detection (read_screen for hung operations), Transcript logging (crShow:,
Friendly Smalltalk development assistant and skill router. Use when the user asks any Pharo/Smalltalk development question, needs help getting started, asks about the workflow, wants to implement/debug/understand code, needs project setup guidance, or is unsure where to begin.
Smalltalk code evaluator for Pharo via MCP. Use when executing Smalltalk expressions, verifying object state or intermediate values, debugging code incrementally, checking Pharo connection, or running quick experiments.
Export package from Pharo image to Tonel files. Use when code was changed directly in Pharo (debugger, browser, or code generation) and needs to be synced back to Tonel files.
| name | st-test |
| description | Run SUnit tests in the running Pharo image. Use when verifying changes after import, or when checking results for a specific test class or package. |
| allowed-tools | mcp__smalltalk-interop__run_class_test mcp__smalltalk-interop__run_package_test mcp__smalltalk-interop__list_packages |
Execute SUnit tests after importing changes to Pharo.
/st-test TestClassName # run a single test class
/st-test PackageName-Tests # run all tests in a package
RsJsonTest) → call run_class_testRediStick-Json-Tests) → call run_package_testWhen no arguments are given, discover and run all test packages automatically:
Locate the source directory — read .project from the repository root and extract the srcDirectory value. Resolve it to an absolute path.
Identify test packages — find the BaselineOf package inside the source directory (a directory starting with BaselineOf) and read its BaselineOfXXX.class.st. Parse the baseline: spec method and collect all packages whose names end with -Tests (or follow the project's test-naming convention).
Check what is already imported — call list_packages to get the list of packages currently loaded in the Pharo image.
Run tests for imported packages — for each test package that is present in the image, call run_package_test and report the pass/fail results.
Report unimported packages — for any test package found in the BaselineOf but not loaded in the image, skip running tests and report it to the user with a note that they can run /st-import first to load it.
/st-test RsJsonTest
/st-test RediStick-Json-Tests