Agent skill

Rigor Monkeypatch Resolve

by rigortype in rigortype/rigor

Resolve Rigor diagnostics caused by literal def methods in a project's own monkey-patches by wiring their files into preeval:.

MPL-2.0Auto-check passedDevelopment

Install Rigor Monkeypatch Resolve

skills CLI
$ npx skills add rigortype/rigor --skill rigor-monkeypatch-resolve -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rigortype/rigor rigor-monkeypatch-resolve --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/rigor-monkeypatch-resolve .claude/skills/rigor-monkeypatch-resolve && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
rigor-monkeypatch-resolve
GitHub stars
106
Token cost
~858 tokens
SKILL.md length
394 words
Files
1
Skills in repo
36
Repo updated
First seen
Licence
MPL-2.0

At a glance

Resolve Rigor diagnostics caused by literal def methods in a project's own monkey-patches by wiring their files into preeval:.

  • Works in 3 steps: confirm it is a monkey-patch cluster → wire the file(s) into pre_eval → verify the cluster cleared
  • Project core extensions cause undefined-method findings
  • SKILL.md covers First: load the…, When to use, When NOT to use and Procedure, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Rigor Monkeypatch Resolve is an agent skill from rigortype/rigor. Resolve Rigor diagnostics caused by literal def methods in a project's own monkey-patches by wiring their files into preeval:. Use when project core extensions cause undefined-method findings; not for dynamic method generation or an external gem without RBS.

Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: Inference-first static analysis for Ruby. The licence is MPL-2.0.

When your agent uses it

  • Project core extensions cause undefined-method findings
  • Not for dynamic method generation
  • An external gem without RBS

Example prompts

  • “/rigor-monkeypatch-resolve”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. confirm it is a monkey-patch cluster
  2. wire the file(s) into pre_eval
  3. verify the cluster cleared

What it can do on your machine

Read from SKILL.md and the folder at commit 57a67cf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rigor Monkeypatch Resolve loads about 858 tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 394 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~858

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rigortype/rigor at commit 57a67cf, republished under its MPL-2.0 licence (© rigortype). 394 words, ~858 tokens.

Download SKILL.mdSave it as .claude/skills/rigor-monkeypatch-resolve/SKILL.md (or your agent's skills folder).
name
rigor-monkeypatch-resolve
description
Resolve Rigor diagnostics caused by literal `def` methods in a project's own monkey-patches by wiring their files into `pre_eval:`. Use when project core extensions cause undefined-method findings; not for dynamic method generation or an external gem without RBS.
license
MPL-2.0
metadata.version
0.1.0
metadata.homepage
https://github.com/rigortype/rigor

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:

sh
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

Show full SKILL.md (167 more words)Show less
Phase 1 — confirm it is a monkey-patch cluster
sh
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..

Phase 2 — wire the file(s) into pre_eval:

Add the defining file paths to pre_eval: in .rigor.dist.yml (paths are resolved relative to the config file):

yaml
pre_eval:
  - lib/core_ext/string.rb
  - lib/core_ext/integer.rb

List the files that contain the defs, not the call sites.

Phase 3 — verify the cluster cleared
sh
rigor check

The call.undefined-method cluster on those methods should be gone. If some survive, those specific methods are almost certainly dynamically generated — pre_eval: cannot reach them, and the durable fix is a project plugin (hand off to rigor-plugin-author). A genuine typo (a real undefined method) correctly keeps firing — do not add it to pre_eval:.

Next step

Re-run rigor skill describe. With the monkey-patch noise gone, the remaining diagnostics are a cleaner target for rigor-baseline-reduce or rigor-protection-uplift.

© rigortype, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/rigor-monkeypatch-resolve of rigortype/rigor.

Open the folder on GitHubat commit 57a67cf

Compare with similar skills

Rigor Monkeypatch Resolve next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rigor Monkeypatch Resolve compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rigor Monkeypatch Resolve this skillrigortype/rigor106—~858Automated safety check: PassMPL-2.0
Vercel Composition Patternssupabase/supabase111k59 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from rigortype/rigor

All 36 skills in this repo
  • Rigor Regression Sweep

    rigortype/rigor

    Measure Rigor's baseline drift across the tagged history of a real OSS Ruby project.

    106 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Adjudicate a rigor unused report safely before proposing dead-code removal.

    106 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Rigor Baseline Reduce

    rigortype/rigor

    Reduce an existing .rigor-baseline.yml rule by rule by triaging sites, fixing or intentionally suppressing them, and regenerating the baseline.

    106 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Rigor Doctor

    rigortype/rigor

    Validate that a project's Rigor configuration, plugins, paths, and baseline are actually healthy.

    106 GitHub stars~767 tokensUpdated today
    Auto-check passed
  • Rigor Plugin Author

    rigortype/rigor

    Author a new Rigor plugin, choosing plugins/ for production support or examples/ for a contract walkthrough.

    106 GitHub stars~3.3k tokensUpdated today
    Auto-check: notes
  • Rigor Plugin Author

    rigortype/rigor

    Author a Rigor plugin in an adopting project or standalone rigor- gem for a DSL, framework, or metaprogramming pattern.

    106 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Categories

Questions about Rigor Monkeypatch Resolve

What does Rigor Monkeypatch Resolve do?

Resolve Rigor diagnostics caused by literal def methods in a project's own monkey-patches by wiring their files into preeval:. Rigor Monkeypatch Resolve is an agent skill from rigortype/rigor. Resolve Rigor diagnostics caused by literal def methods in a project's own monkey-patches by wiring their files into preeval:.

When should I use Rigor Monkeypatch Resolve?

Rigor Monkeypatch Resolve fits situations like: project core extensions cause undefined-method findings; not for dynamic method generation; an external gem without RBS.

How do I install Rigor Monkeypatch Resolve in Claude Code?

Run `npx skills add rigortype/rigor --skill rigor-monkeypatch-resolve -a claude-code`. Or copy the skill folder (skills/rigor-monkeypatch-resolve in rigortype/rigor) into .claude/skills/rigor-monkeypatch-resolve in your project. Claude Code loads it when a task matches its description.

How do I install Rigor Monkeypatch Resolve in Codex?

Run `npx skills add rigortype/rigor --skill rigor-monkeypatch-resolve -a codex`. Or copy the skill folder (skills/rigor-monkeypatch-resolve in rigortype/rigor) into .agents/skills/rigor-monkeypatch-resolve in your project. Codex loads it when a task matches its description.

Can I use Rigor Monkeypatch Resolve in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rigortype/rigor --skill rigor-monkeypatch-resolve -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rigor-monkeypatch-resolve, .gemini/skills/rigor-monkeypatch-resolve, .github/skills/rigor-monkeypatch-resolve and .opencode/skills/rigor-monkeypatch-resolve in your project.

What does Rigor Monkeypatch Resolve need to run?

SKILL.md names no scripts, command-line tools or credentials: Rigor Monkeypatch Resolve is instructions for the agent only.

Does Rigor Monkeypatch Resolve access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Rigor Monkeypatch Resolve safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Rigor Monkeypatch Resolve use?

Rigor Monkeypatch Resolve is published under the MPL-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rigor Monkeypatch Resolve use?

About 858 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Rigor Monkeypatch Resolve?

Skills that share tags, products or a category with Rigor Monkeypatch Resolve: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rigor Monkeypatch Resolve?

rigortype (a GitHub organization) maintains it in rigortype/rigor, which has 106 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 8, 2026.

Source: rigortype/rigor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.