rigor-monkeypatch-resolve

Rigor Monkeypatch Resolve

When a project adds methods to existing classes in its own files — the classic lib/core_ext/*.rb class String; def squish; …; end pattern — Rigor does not see them unless told to, so every call to the added method fires call.undefined-method (or call.unresolved-toplevel for a top-level helper). pre_eval: (ADR-17) fixes this: it pre-evaluates the listed project files and registers every method they define with a literal def / def self..

First: load the version-current copy

This skill's exact commands, flags, and config keys drift between Rigor releases, so follow the copy that ships with the installed Rigor rather than any vendored or frozen copy of this file. Get the complete current procedure in one call:

rigor skill --full rigor-monkeypatch-resolve

If you already loaded this skill via rigor skill you have the current copy — just proceed. If rigor is not on PATH, this task needs it: run rigor-next-steps to install Rigor first, then come back.

When to use

• rigor triage shows a cluster of call.undefined-method / call.unresolved-toplevel whose receiver is a core class the project monkey-patches (or a top-level helper the project defines).

When NOT to use

• The methods are generated dynamically (define_method with a computed name, method_missing, a class_eval <<~RUBY … def #{name} heredoc). pre_eval: walks for literal defs and will not find them — that residue is a rigor-plugin-author job.
• The cluster is on a third-party gem with no RBS — that is rigor-rbs-setup.

Procedure

Phase 1 — confirm it is a monkey-patch cluster

rigor triage --format json

Look at the selectors / hotspots: a cluster keyed on a core receiver (String#squish, Integer#…) or a top-level helper, all pointing back to a file in your project that defines them. Open that file and confirm the methods are written as literal def / def self..