Agent skill

Rigor Upgrade

by rigortype in rigortype/rigor

Adopt a new rigortype version by comparing its diagnostics with the committed baseline and separating new catches from signature-quality false positives.

MPL-2.0Auto-check passedDevelopment

Install Rigor Upgrade

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

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

GitHub CLI
$ gh skill install rigortype/rigor rigor-upgrade --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-upgrade .claude/skills/rigor-upgrade && 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-upgrade
GitHub stars
106
Token cost
~878 tokens
SKILL.md length
435 words
Files
1
Skills in repo
36
Repo updated
First seen
Licence
MPL-2.0

At a glance

Adopt a new rigortype version by comparing its diagnostics with the committed baseline and separating new catches from signature-quality false positives.

  • Works in 4 steps: confirm the new version → see the delta against the committed… → sort the new diagnostics → …
  • Development work in your project
  • SKILL.md covers First: load the…, When to use, Procedure and Note, plus 1 more section
  • Calls mise and gem

What it does

Rigor Upgrade is an agent skill from rigortype/rigor. 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.

Its SKILL.md is about 880 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

  • Development work in your project

Example prompts

  • “/rigor-upgrade”

Workflow steps

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

  1. confirm the new version
  2. see the delta against the committed baseline
  3. sort the new diagnostics
  4. regenerate the baseline (acknowledge mode)

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

    Shell commands in SKILL.md call:

    • mise
    • gem

    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 Upgrade loads about 878 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 435 words of instructions outside code blocks.

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

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). 435 words, ~878 tokens.

Download SKILL.mdSave it as .claude/skills/rigor-upgrade/SKILL.md (or your agent's skills folder).
name
rigor-upgrade
description
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.
license
MPL-2.0
metadata.version
0.1.0
metadata.homepage
https://github.com/rigortype/rigor

Rigor Upgrade

A new Rigor release sharpens inference and may add or tighten rules, so rigor check can report diagnostics it did not before — most are the new version catching more, a few are sig-quality false positives the new sharpness exposes. This skill adopts the upgrade without either blindly regenerating the baseline (which buries genuine new catches) or treating every new line as a regression.

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 — doubly so here, since you just changed the version this skill is meant to track. Get the complete current procedure in one call:

sh
rigor skill --full rigor-upgrade

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

  • You just ran mise use gem:rigortype / gem update rigortype and want to understand what the new version changed about your project's diagnostics.

Procedure

Phase 1 — confirm the new version
sh
rigor --version
Phase 2 — see the delta against the committed baseline
sh
rigor check             # everything outside the committed baseline's envelope
rigor baseline drift    # per-bucket movement against .rigor-baseline.yml

With baseline: wired, rigor check already hides what the baseline covers, so what it prints is new relative to the baseline — that set is what the upgrade changed. rigor baseline drift adds the bucket view: buckets now over their recorded count, and buckets the new version cleared or shrank.

Show full SKILL.md (185 more words)Show less
Phase 3 — sort the new diagnostics

For each newly-surfaced diagnostic:

  • A genuine new catch — the sharper inference found a real latent issue. Fix it. (Check evidence_tier in rigor check --format json: high is most likely a true positive.)
  • A sig-quality false positive — a known class (Struct call.wrong-arity, an over-nilable RBS return, a regex-capture $1 read). # rigor:disable <rule> the site with a reason, or address the RBS. Read rigor explain <rule> if unsure whether the rule should fire here.
  • Expected envelope growth — broadly acceptable in acknowledge mode.
Phase 4 — regenerate the baseline (acknowledge mode)

Once you have triaged and fixed the genuine catches, record the new envelope so the regeneration does not bury what you just fixed:

sh
rigor baseline regenerate

Recommend committing the updated .rigor-baseline.yml together with any fixes, so the team adopts the same post-upgrade baseline.

Note

rigor skill describe cannot detect that you just upgraded — the baseline records only its schema version, not the Rigor version that generated it — so this skill is invoked on demand rather than recommended automatically. Run it whenever you bump the gem.

Next step

Re-run rigor skill describe for the next move.

© 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-upgrade of rigortype/rigor.

Open the folder on GitHubat commit 57a67cf

Compare with similar skills

Rigor Upgrade 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 Upgrade compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rigor Upgrade this skillrigortype/rigor106—~878Automated safety check: PassMPL-2.0
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 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 58 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.

    297k 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 yesterday
    Auto-check passed
  • Adjudicate a rigor unused report safely before proposing dead-code removal.

    106 GitHub stars~1.1k tokensUpdated yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    Auto-check passed

Categories

Questions about Rigor Upgrade

What does Rigor Upgrade do?

Adopt a new rigortype version by comparing its diagnostics with the committed baseline and separating new catches from signature-quality false positives. Rigor Upgrade is an agent skill from rigortype/rigor. Adopt a new rigortype version by comparing its diagnostics with the committed baseline and separating new catches from signature-quality false positives.

When should I use Rigor Upgrade?

Rigor Upgrade fits situations like: development work in your project.

How do I install Rigor Upgrade in Claude Code?

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

How do I install Rigor Upgrade in Codex?

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

Can I use Rigor Upgrade 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-upgrade -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-upgrade, .gemini/skills/rigor-upgrade, .github/skills/rigor-upgrade and .opencode/skills/rigor-upgrade in your project.

What does Rigor Upgrade need to run?

Going by SKILL.md and its folder, Rigor Upgrade needs the command-line tools its instructions call (mise and gem).

Does Rigor Upgrade 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 Upgrade 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 Upgrade use?

Rigor Upgrade 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 Upgrade use?

About 878 tokens (SKILL.md is roughly 3.5k 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 Upgrade?

Skills that share tags, products or a category with Rigor Upgrade: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k 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 Upgrade?

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.