Stats
Actions
Tags
From smalltalk-dev
Validates Tonel .st file syntax before importing to Pharo. Use when suspecting syntax errors or after manual edits to ensure correctness.
How this skill is triggered — by the user, by Claude, or both
Slash command
/smalltalk-dev:st-validateThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate Tonel `.st` files before importing to Pharo. Modern AI usually generates correct Tonel, so this is optional.
Validate Tonel .st files before importing to Pharo. Modern AI usually generates correct Tonel, so this is optional.
/st-validate /absolute/path/to/MyClass.st # validate a file
/st-validate 'Tonel source text' # validate content directly
validate_tonel_smalltalk_from_file for a file path, or validate_tonel_smalltalk for raw contentvalidate_smalltalk_method_body to validate a single method body in isolation/st-validate /home/user/project/src/MyPackage/MyClass.st
npx claudepluginhub mumez/smalltalk-dev-plugin --plugin smalltalk-devLints Tonel .st files for Smalltalk best practices before Pharo import, after editing for quality checks, or to diagnose style issues in packages.
Lints Stata .do and .ado files for style and best-practice issues like hardcoded paths, long lines, missing version statements, and improper cd or delimit usage. Suggests modern alternatives.
Runs PHP syntax checking (php -l) on project files to detect parse errors, with fix-then-retest cycles and a report format.