smalltalk-debugger

Debugging a failing test in Pharo involves inspecting the stack trace, checking the receiver's class and available methods, and evaluating code incrementally to isolate the error. This Skill guides you through those steps—using eval to test hypotheses, searching for method implementations, and analyzing intermediate values to pinpoint the root cause.

MessageNotUnderstood occurs when code calls a method that doesn't exist on an object. Debugging this error requires checking the receiver's class, verifying the method name, and confirming the method is actually implemented. This Skill automates that investigation process.

Inspecting object state means examining an object's instance variables, collections, and dictionaries at runtime. This Skill provides structured procedures for using the debugger to read object properties, verify data integrity, and understand how runtime values led to the error.

Yes. This Skill automates diagnosis of Pharo Smalltalk test failures by recognizing common error patterns, suggesting incremental evaluation strategies, and guiding debugger-window analysis to resolve issues faster than manual investigation alone.

This Skill addresses MessageNotUnderstood, KeyNotFound, SubscriptOutOfBounds, timeouts, and unresponsive images. It applies structured root-cause analysis to each error type using source inspection, method search, and controlled code evaluation.

Yes. This Skill is designed specifically for Pharo Smalltalk runtime environments. It requires access to a running Pharo image and uses its debugger, eval, and source-inspection tools to diagnose and resolve errors.