Smalltalk Debugger
Pharo/Smalltalk error-diagnosis and Transcript-logging workflow for AI coding agents.
Działa po konfiguracji
Co robi ten skill
Gives an AI editor a systematic Pharo Smalltalk debugging playbook: classify the error (MessageNotUnderstood, KeyNotFound, SubscriptOutOfBounds, AssertionFailure), reproduce incrementally via an eval tool, inspect intermediate values safely, detect stuck UI debugger windows, and log through Transcript in headless/Docker images. Triggers on Pharo test failures, Smalltalk exceptions, hangs during MCP calls, or requests to add debug logging/trace call sites.
Raport z testu
Solid Pharo-specific debugging playbook (Tonel-only edits, printString-safe MCP returns, NonInteractiveTranscript for headless output) that clearly beats generic debugging advice on a real comparison — but it only does anything wired to the plugin's smalltalk-interop/smalltalk-validator MCP servers and a live Pharo image, none of which travel with a standalone copy of just the skill folder.
Testowano: 2026-07-15 · Claude Code 2.x (agent harness)
Instalacja
git clone https://github.com/mumez/smalltalk-dev-plugin mkdir -p ~/.claude/skills cp -r smalltalk-dev-plugin/skills/smalltalk-debugger ~/.claude/skills/smalltalk-debugger
Komendy i przykładowe prompty
/smalltalk-debuggerPharo/Smalltalk error-diagnosis and Transcript-logging workflow for AI coding agents.
Skille uruchamiają się na zwykłe polecenia — bez komend do zapamiętania. Po instalacji aktywują go prompty takie jak te (po angielsku):
My Pharo test throws MessageNotUnderstood and I can't figure out whyGetting a KeyNotFound error in my Smalltalk Dictionary lookup, please helpThe Pharo debugger window seems stuck again during this MCP call