Vb6 Trace Pattern

Applies the manual stack-trace pattern for Visual Basic 6 based on EnterMethod/ExitMethod calls that push and pop method names from a module-level array. This pattern compensates for the absence of a native call stack in VB6, enabling rich production logs with call depth, parameter serialization, and on-demand stack inspection in error handlers. Covers when to instrument procedures (every non-trivial function), placement rules (EnterMethod in EhHeader, ExitMethod in both success and error paths), optional parameter serialization, the TraceMethod function for inserting the current stack into error messages, log file management (rolling daily logs with retention), activation gating (only logs when explicitly enabled or running in the IDE), and automatic process dumping via WMI when automation errors are detected. Activates whenever working with EnterMethod, ExitMethod, LogMsg, TraceMethod, manual stack trace, or any VB6 task involving production diagnostics, error logging, debugging, or fault investigation.

mkdir -p ~/.claude/skills/vb6-trace-pattern
curl -L https://claudskills.com/skills/vb6-trace-pattern/SKILL.md \
  -o ~/.claude/skills/vb6-trace-pattern/SKILL.md

@misc{vb6-trace-pattern-2026,
  author    = {alexcassol},
  title     = {Vb6 Trace Pattern [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/vb6-trace-pattern/}
}