Menu
Import Tonel package into running Pharo image. Use when loading edited .st files into Pharo after code changes.
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
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.
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-import |
| description | Import Tonel package into running Pharo image. Use when loading edited .st files into Pharo after code changes. |
| allowed-tools | mcp__smalltalk-interop__import_package mcp__smalltalk-validator__validate_tonel_smalltalk_from_file |
Import edited Tonel files into the running Pharo image.
/st-import PackageName /absolute/path/to/src
import_package with the package name and absolute path to the src/ directoryWhen no arguments are given, discover and import the full project automatically:
Locate the source directory — read .project from the repository root. It contains JSON-like Pharo syntax with a srcDirectory key (e.g., 'srcDirectory' : 'src'). Resolve the value relative to the repository root to get the absolute path to the source directory.
Determine import order — find the BaselineOf package inside the source directory (a directory whose name starts with BaselineOf). Read the BaselineOfXXX.class.st file inside it and parse the baseline: spec method. Extract:
package: 'PkgName' declarations → the full list of packages to importrequires: #('Dep1' 'Dep2' ...) clauses → the dependency edges between packagesTopologically sort the packages so that each package is imported only after all its dependencies have been imported. Import the BaselineOf package first (before all others), then the sorted application packages.
Import each package — call import_package for each package in the computed order, passing the absolute path to the source directory. Report the result of each import as you go.
/st-import RediStick-Json /home/user/git/RediStick/src
/st-import RediStick-Json-Tests /home/user/git/RediStick/src