St export
Claude Code plugin for AI-driven Smalltalk (Pharo) development
npx -y skills add mumez/smalltalk-dev-plugin --skill st-exportAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.1 KB, as published. Nobody here has run it
Export Package from Pharo
Export a package from the running Pharo image back to Tonel files.
Usage
/st-export PackageName /absolute/path/to/src
Steps
- Call
export_packagewith package name and absolute path to thesrc/directory - Report the exported files or any error
When to Use
Export is the exception, not the norm. Use only when Pharo has newer code than Tonel files:
- Fixed code in the Pharo debugger
- Generated boilerplate using Pharo tools
- Made changes directly in the Pharo browser
Notes
- Normally, edit Tonel files and import — AI editor is the source of truth
- Export overwrites existing
.stfiles in the directory - Always use absolute paths
Examples
/st-export MyPackage /home/user/project/src
/st-export MyPackage-Tests /home/user/project/src