Tips for Best Results
A few habits that consistently get sharper, more grounded answers out of RubberDuck.
Load before querying
Always make sure your code is loaded with load_code before running analysis.
Be specific
"Trace the data flow of request in handle_upload" works better than "Tell me about the code."
Check what's loaded
If results seem incomplete, ask: Call list_loaded to show me what's currently loaded.
Trust the tags
Results tagged with [data-flow], [call-chain], [source-match] come from deep code analysis.
Narrow scope works best
RubberDuck is strongest when the task is bounded: a specific function, bug, or change.
Iterative refinement
If the first analysis is too broad, follow up with a more targeted prompt.