Inference-first static analysis for Ruby
This repository also configures its own agents. See what rigor tells them →
Skill Claude CodeCodex
Set direction and LaneInput contracts for a scoped Rigor change (issue-shaped). Use for planning and acceptance only — not large implementation diffs, CI watch, or merge judgment. Finish with Plan ready or Blocked — need human.
Skill Claude CodeCodex
Docs-only Rigor work: JA site publish and EN docs polish. No engine behaviour changes or type-spec rewrites disguised as prose. Finish Docs ready or Blocked — need human.
Skill Claude CodeCodex
Select Issues, assign lanes, own CI watching / merge judgment for the Rigor pi harness. Prefer sparse gh status polls; external poll + resume is OK. Issues remain the ADR-98 backlog. Do not run parallel host make verify.
Skill Claude CodeCodex
A workflow for reducing an existing Rigor baseline, a file that records already-accepted analysis findings. It reviews findings rule by rule, fixes or intentionally suppresses them, reports issues, and regenerates the baseline.
Skill Claude CodeCodex
Answer a question about Rigor from version-matched bundled docs and tool output. Use when the user asks why a diagnostic fired, how a type/config/flag works, or how Rigor compares with another tool; not when they ask you to set up, fix, or reduce something.
Skill Claude CodeCodex
Reduce an existing .rigor-baseline.yml rule by rule by triaging sites, fixing or intentionally suppressing them, and regenerating the baseline. Use for baseline diagnostics already acknowledged by a project; not for first-time setup or plugin authoring.
Skill Claude CodeCodex
Set up Rigor in a project's CI and surface diagnostics on pull or merge requests. Use when adding or changing GitHub Actions, GitLab CI, SARIF, or reviewdog wiring; not for first-time Rigor configuration or baseline reduction.
Skill Claude CodeCodex
Validate that a project's Rigor configuration, plugins, paths, and baseline are actually healthy. Use when diagnostics are suspicious or setup behavior is wrong; not for first-time onboarding or reducing ordinary diagnostics.
Skill Claude CodeCodex
Set up Rigor's bundled language server for live diagnostics, hover, outline, and completion in a developer's editor. Use when wiring rigor lsp into VS Code, Neovim, Helix, Emacs, or another LSP client; not for CI or first-time project setup.
Skill Claude CodeCodex
Set up Rigor's bundled MCP server for an AI coding agent and verify the connection. Use when wiring rigor mcp into Claude Code, Cursor, Cline, or another MCP client; not for editor LSP or CI setup.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Route a project to its next Rigor step, installing or onboarding Rigor when needed and then delegating to rigor skill describe. Use when the user asks where to start or what to do next with Rigor; not instead of a task-specific skill the route selects.
Skill Claude CodeCodex
Audit an existing Rigor plugin against the current authoring contract and produce a prioritized upgrade path. Use when modernizing or reviewing a rigor- plugin; not for authoring a new plugin, enabling bundled plugins, or tuning project config.
Skill Claude CodeCodex
Match a configured project's Gemfile.lock to Rigor's bundled plugin catalogue and enable the plugins its current dependencies need. Use after adding a gem or when plugin selection is stale; not for first-time onboarding or authoring a new plugin.
Skill Claude CodeCodex
Onboard a project to Rigor from scratch by detecting the stack, selecting plugins and an adoption mode, and writing the initial config and baseline or strict gate. Use for first-time Rigor setup; not for an existing baseline or plugin authoring.
Skill Claude CodeCodex
Close the protection gaps reported by rigor coverage --protection, using generated signatures before minimal residual annotations and a no-new-diagnostics gate. Use when increasing bug-catching coverage in an adopting project; not for Rigor's own tree, bundled plugins, or first-time setup.
Skill Claude CodeCodex
Install community RBS for a project's gems so Rigor can type dependencies that currently become Dynamic. Use when rbs collection is missing or untyped gems limit coverage; not for first-time Rigor setup or a gem with no community RBS entry.
Skill Claude CodeCodex
Obtain a Ruby type from Rigor before writing or asserting it, using type-of, annotate, or sig-gen as appropriate. Use when adding RBS, inline annotations, Sorbet/YARD types, type-shaped docs, or type-justified guards; not for Rigor setup or baseline reduction.
Skill Claude CodeCodex
Adjudicate a rigor unused report safely before proposing dead-code removal. Use when interpreting or reviewing Rigor's unused classes/modules/constants, or when a cleanup is based on that report; not for a specific deletion already known to be safe or for ordinary rigor check diagnostics.
Skill Claude CodeCodex
Adopt a new rigortype version by comparing its diagnostics with the committed baseline and separating new catches from signature-quality false positives. Use after a Rigor gem upgrade; not for first-time setup or routine baseline reduction.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: