St lint
Smalltalk best-practices linter for Tonel files. Use when validating .st files before importing to the Smalltalk image (Pharo or Squeak), checking code quality after editing, or diagnosing style issues in a package.From its SKILL.md
npx -y skills add mumez/smalltalk-dev-plugin --skill st-lintAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 15 stars15 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.
SKILL.md
3.5 KB, as published. Nobody here has run it
Lint Tonel Files
Validate Tonel .st files for Smalltalk best practices before importing to the Smalltalk image.
When to Use
- Before every
/st-import— lint catches issues that would silently corrupt the image - After editing
.stfiles — confirm no style regressions - When import fails with unexpected behavior — lint may reveal the root cause
Step 1: Check Meta Files (manual — MCP cannot validate these)
Before linting, verify required Tonel meta files exist:
| File | Location | Required |
|---|---|---|
.project | repo root | ✅ |
src/.properties | src/ directory | ✅ |
package.st | each package directory | ✅ |
If any are missing, warn the user, suggest /st-setup-project, and continue linting — lint results are still useful even when meta files are absent, since the linter operates on .st file syntax independently.
Expected src/.properties content:
{
#format : #tonel
}
Step 2: Collect .st Files
Resolve the target to a list of absolute paths:
- Single file (
src/MyPackage/MyClass.st): use directly, skip if it ispackage.st - Package directory (
src/MyPackage): Glob**/*.st, excludepackage.st - src root (
src): Glob**/*.stacross all packages, excludepackage.st
Always convert to absolute paths before passing to the MCP tool.
Step 3: Lint Each File
Call mcp__smalltalk-validator__lint_tonel_smalltalk_from_file with the absolute path, one file at a time.
Step 4: Report Results
Show a summary per file:
src/MyPackage/MyClass.st — ✅ clean
src/MyPackage/AnotherClass.st — ⚠️ 2 warnings
• [warning] Method #doSomething has no comment
• [warning] Temporary variable 'x' shadows outer scope
src/MyPackage/BrokenClass.st — ❌ 1 error
• [error] Syntax error near ']'
Exit status semantics:
| Result | Meaning | Action |
|---|---|---|
| 0 — clean | No issues | Proceed to import |
| 1 — warnings only | Style issues | Proceed to import, consider fixing |
| 2 — errors found | Syntax/structural errors | Fix before importing |
If any warning flags a class as missing or having a poor class comment, offer to invoke smalltalk-dev:smalltalk-commenter to generate a CRC-style comment for the affected class(es) rather than leaving the user to write it manually.
Interpreting Common Issues
| Issue | Likely Cause | Fix |
|---|---|---|
Syntax error near '...' | Unclosed bracket/paren, missing period | Check the indicated line |
Method has no comment | Missing method comment | Add a brief comment |
Class has no comment / Missing class comment | Missing or inadequate class comment | Suggest running smalltalk-dev:smalltalk-commenter to generate a CRC-style comment |
Temporary variable shadows outer scope | Variable name collision | Rename the temp var |
Missing package.st | package.st not found | Create it: Package { #name : 'PkgName' } |
Related Skills
smalltalk-dev:st-setup-project— Create missing meta filessmalltalk-dev:smalltalk-developer— Full Edit → Lint → Import → Test workflowsmalltalk-dev:smalltalk-commenter— Generate CRC-style class comments when lint flags classes with missing/poor comments
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most quality gates skills give
Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06
- Read full output and check exit codein 45 of 1524, across 40 files
- Verify output confirms the claimin 44 of 1524, across 39 files
- Identify the command that proves the claimin 43 of 1524, across 39 files
- Execute the full verification commandin 36 of 1524, across 30 files
- Produce a verification reportin 34 of 1524, across 18 files
- Review git diff changesin 30 of 1524, across 16 files
- Fix build failures immediatelyin 29 of 1524, across 9 files
- Group findings by severityin 28 of 1524
- State claim only with evidencein 27 of 1524, across 22 files
- Verify regression tests with red-green cyclein 26 of 1524, across 22 files
- Run the full test suitein 26 of 1524, across 25 files
- Run test suite with coveragein 25 of 1524, across 10 files
Said here and by no other author read
- Verify existence of required Tonel meta files
- Warn user if meta files are missing
- Exclude package.st files from linting
- Lint files one at a time
- Report linting results per file
- Offer to generate comments for classes with missing comments
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.