Breaking Change Analysis
ruby-git/ruby-git
Assesses what an API change would break before it is made, finds every usage, documents the impact and plans a deprecation or migration path.
Add or repair a read-only upstream submodule under references/.
$ npx skills add rigortype/rigor --skill rigor-add-reference -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rigortype/rigor rigor-add-reference --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/rigor-add-reference .claude/skills/rigor-add-reference && rm -rf skills-srcUse ~/.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/
Install the "rigor-add-reference" agent skill from https://github.com/rigortype/rigor/tree/master/.claude/skills/rigor-add-reference into .claude/skills/rigor-add-reference/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-add-reference", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rigortype/rigor/tree/master/.claude/skills/rigor-add-referenceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rigortype/rigor --skill rigor-add-reference -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rigortype/rigor rigor-add-reference --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/rigor-add-reference .agents/skills/rigor-add-reference && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rigor-add-reference" agent skill from https://github.com/rigortype/rigor/tree/master/.claude/skills/rigor-add-reference into .agents/skills/rigor-add-reference/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-add-reference", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rigortype/rigor --skill rigor-add-reference -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rigortype/rigor rigor-add-reference --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/rigor-add-reference .cursor/skills/rigor-add-reference && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "rigor-add-reference" agent skill from https://github.com/rigortype/rigor/tree/master/.claude/skills/rigor-add-reference into .cursor/skills/rigor-add-reference/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-add-reference", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rigortype/rigor.git --path .claude/skills/rigor-add-reference--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rigortype/rigor --skill rigor-add-reference -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rigortype/rigor rigor-add-reference --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/rigor-add-reference .gemini/skills/rigor-add-reference && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "rigor-add-reference" agent skill from https://github.com/rigortype/rigor/tree/master/.claude/skills/rigor-add-reference into .gemini/skills/rigor-add-reference/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-add-reference", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rigortype/rigor rigor-add-referenceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rigortype/rigor --skill rigor-add-reference -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/rigor-add-reference .github/skills/rigor-add-reference && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "rigor-add-reference" agent skill from https://github.com/rigortype/rigor/tree/master/.claude/skills/rigor-add-reference into .github/skills/rigor-add-reference/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-add-reference", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rigortype/rigor --skill rigor-add-reference -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rigortype/rigor rigor-add-reference --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/rigor-add-reference .opencode/skills/rigor-add-reference && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "rigor-add-reference" agent skill from https://github.com/rigortype/rigor/tree/master/.claude/skills/rigor-add-reference into .opencode/skills/rigor-add-reference/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-add-reference", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
rigor-add-referenceAdd or repair a read-only upstream submodule under references/.
Rigor Add Reference is an agent skill from rigortype/rigor. Add or repair a read-only upstream submodule under references/. Use when adding a reference checkout or diagnosing its clone, status, rename, or lifecycle failure; not for product code or ordinary dependency updates.
Its SKILL.md is about 2.1k 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, covering Dependency management. It works with Ruby and Git. The repository describes itself as: Inference-first static analysis for Ruby. The licence is MPL-2.0.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c7b6b60. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
gitmakergnixFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Rigor Add Reference loads about 2.1k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 867 words of instructions outside code blocks.
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.
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.
The full file from rigortype/rigor at commit c7b6b60, republished under its MPL-2.0 licence (© rigortype). 867 words, ~2,125 tokens.
.claude/skills/rigor-add-reference/SKILL.md (or your agent's skills folder).Use this skill when the user wants to add a new upstream repo under references/. The change always touches three things together: .gitmodules (via git submodule add), Makefile (REFERENCE_SUBMODULES list + init-submodules body), and the submodule pointer commit. They belong in a single commit.
The standing rule is in AGENTS.md: these submodules are read-only reference material, not Rigor code — never require, import, or copy upstream implementation into product code; read the behaviour, then implement the smallest Rigor-side equivalent. Update a submodule only when intentionally changing the referenced revision.
| Submodule | Upstream | Use |
|---|---|---|
references/rbs | https://github.com/ruby/rbs.git | RBS syntax, stdlib signatures, test cases, implementation behaviour. The compatibility target for the RBS ecosystem. |
references/python-typing | https://github.com/python/typing.git | Written-down Python typing concepts (gradual typing, generics, protocols, variance), borrowed by idea only. Not a syntax compatibility target. |
references/ruby | https://github.com/ruby/ruby.git (branch ruby_4_0) | Ruby interpreter source. Parsed offline to derive the PHPStan-functionMap-style catalog of built-in methods: argument / return types plus per-method effect facets (pure, self-mutating, block-dependent). Never link Rigor runtime code against it. |
references/typeprof | https://github.com/ruby/typeprof.git | TypeProf source — the reference implementation of Ruby type inference. Read for ideas and behaviour comparisons; never import or require it. |
The trees are large, so the root .ignore lists /references/ to keep rg out by default (git is unaffected). Search one intentionally, and scope the path so you do not pull in vendor/:
rg PATTERN --no-ignore references/rbsBefore running any command, ask (or infer from context) whether a sparse checkout is needed:
git submodule update --init --filter=blob:none.references/phpstan needs only website/, references/TypeScript-Website needs only packages/documentation/copy/en). Use the sparse-checkout pattern from init-submodules in the Makefile.When in doubt, full checkout is fine. Sparse is an optimisation, not a correctness requirement.
git submodule add <upstream-url> references/<name>Use https:// URLs for read-only public repos (like sorbet). Use git@github.com: SSH URLs for repos where write access is possible or expected (like the existing ruby/typeprof). Match the convention of whichever group the new submodule belongs to.
This writes the .gitmodules entry and stages references/<name> automatically.
Edit Makefile in two places:
REFERENCE_SUBMODULES list (used by make pull-submodules)Append the new entry at the end of the list, continuing the \-continuation style:
REFERENCE_SUBMODULES := \
references/rbs \
... \
references/typeprof \
references/<name> # ← add hereinit-submodules target bodyFull checkout — add one line after the last simple git submodule update line (before the @if sparse-checkout blocks):
git submodule update --init --filter=blob:none references/<name>Sparse checkout — add an @if block modelled on the existing phpstan or TypeScript-Website blocks. The structure is:
@if [ ! -e references/<name>/.git ]; then \
url="$$(git config -f .gitmodules submodule.references/<name>.url)"; \
sha="$$(git rev-parse HEAD:references/<name>)"; \
echo "Initializing references/<name> sparsely (<which-subdirectory>)"; \
git clone --no-checkout --filter=blob:none "$$url" references/<name>; \
git -C references/<name> fetch origin "$$sha"; \
git -C references/<name> sparse-checkout init --cone; \
git -C references/<name> sparse-checkout set <subdirectory>; \
git -C references/<name> checkout --detach "$$sha"; \
git submodule absorbgitdirs references/<name>; \
else \
git submodule update --init --filter=blob:none references/<name>; \
fiThe absorbgitdirs call is required for sparse-checkout blocks because git clone puts the .git directory inside the worktree rather than under .git/modules/.
git statusExpected staged files:
modified: .gitmodulesmodified: Makefilenew file: references/<name> (the submodule pointer)No other files should be staged. If references/<name>/ appears as untracked content rather than a submodule pointer, the git submodule add in Step 1 didn't complete cleanly — re-run it.
Commit all three together. Subject line format (plain imperative, no prefix):
Add references/<name> submoduleBody (optional, include if the purpose isn't obvious from the name):
Wire <name> into REFERENCE_SUBMODULES and init-submodules so
make pull-submodules and make init-submodules keep it in sync
automatically.git submodule add ran successfully and references/<name> is initialised.REFERENCE_SUBMODULES in Makefile includes references/<name>.init-submodules in Makefile has the correct block for the chosen checkout strategy.git status shows exactly the three expected staged entries..gitmodules, Makefile, and references/<name> — nothing else.Drive the lifecycle through the Make targets: make init-submodules, make pull-submodules. Avoid raw git submodule update --recursive against the whole tree — it bypasses the sparse-checkout setup init-submodules bakes in for references/phpstan and references/TypeScript-Website. If a submodule is empty after cloning, run nix develop --command make init-submodules.
Never hand-edit .gitmodules or .git/config for a rename. Use git mv old/path new/path, then git submodule sync so .git/config follows .gitmodules. Hand edits leave stale submodule.<name>.* sections and orphan .git/modules/<old>/ directories, which can crash later parent operations with a submodule.c BUG assertion.
make setup runs make init-git-config, which is idempotent and writes only to this clone's .git/config. What it sets and why:
submodule.recurse = false — parent operations (reset, checkout, pull) do not recurse, so one broken submodule cannot abort a parent-side git reset --hard.fetch.recurseSubmodules = on-demand — git fetch pulls submodule objects only when parent commits need them.status.submoduleSummary = true, diff.submodule = log — pointer changes show up instead of being silent.push.recurseSubmodules = check — git push refuses if a referenced submodule commit is not pushed upstream.Run make doctor-submodules first when anything looks off (git status failing, parent operations exploding on a submodule). It detects stale .git/config sections with no .gitmodules entry, dangling .git pointers in submodule worktrees, orphaned .git/modules/<name>/ directories, and incomplete gitdirs (missing HEAD or objects). It reports and suggests; it changes nothing itself.
Then, after a backup if anything looks valuable:
| Breakage | Fix |
|---|---|
Stale .git/config section (renamed away in .gitmodules) | git config --remove-section submodule.<old/name> |
Orphaned .git/modules/<name>/ (no longer in .gitmodules) | rm -rf .git/modules/<name> after confirming nothing references it |
Submodule worktree .git points at a missing / incomplete gitdir | git submodule deinit -f <path>, then make init-submodules to re-clone |
Parent git reset aborts on submodule recursion | Should not happen once make init-git-config has run; escape hatch is git -c submodule.recurse=false reset --hard <ref> |
© 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
Just SKILL.md in .claude/skills/rigor-add-reference of rigortype/rigor.
Open the folder on GitHubat commit c7b6b60
Rigor Add Reference 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Rigor Add Reference this skillrigortype/rigor | 106 | — | ~2.1k | Automated safety check: Pass | MPL-2.0 | |
| Breaking Change Analysisruby-git/ruby-git | 1.8k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Gem Dependency Managementruby-git/ruby-git | 1.8k | — | ~806 | Automated safety check: Pass | MIT | |
| Ghostty Submodule and GhosttyKit Workflowmanaflow-ai/cmux | 28k | 1 repos | ~580 | Automated safety check: Pass | Custom licence | |
| GitVersion .NET DevelopmentGitTools/GitVersion | 3.1k | — | ~1.7k | Automated safety check: Pass | MIT | |
| OBS Plugin Dependency Upgradesorayuki/obs-multi-rtmp | 5.1k | — | ~609 | Automated safety check: Pass | GPL-2.0 |
ruby-git/ruby-git
Assesses what an API change would break before it is made, finds every usage, documents the impact and plans a deprecation or migration path.
ruby-git/ruby-git
Workflow for updating gem dependencies and fixing CVEs in the ruby-git project: assess with bundle outdated and audit, edit the gemspec, test, then commit with conventional messages.
manaflow-ai/cmux
Workflow rules for the Ghostty submodule in cmux: rebuilding GhosttyKit.xcframework, pushing fork changes and updating the parent submodule pointer safely.
GitTools/GitVersion
Gives repository-specific .NET guidance for GitVersion: build and test commands, central package management, project layout and coding conventions.
sorayuki/obs-multi-rtmp
Updates the obs-multi-rtmp plugin repo to the latest upstream plugin template and OBS Studio version, including dependency metadata, then rebuilds it with CMake.
Asvarox/allkaraoke
Smart dependency management for any language. An agent skill from Asvarox/allkaraoke.
rigortype/rigor
Measure Rigor's baseline drift across the tagged history of a real OSS Ruby project.
rigortype/rigor
Adjudicate a rigor unused report safely before proposing dead-code removal.
rigortype/rigor
Reduce an existing .rigor-baseline.yml rule by rule by triaging sites, fixing or intentionally suppressing them, and regenerating the baseline.
rigortype/rigor
Validate that a project's Rigor configuration, plugins, paths, and baseline are actually healthy.
rigortype/rigor
Author a new Rigor plugin, choosing plugins/ for production support or examples/ for a contract walkthrough.
rigortype/rigor
Author a Rigor plugin in an adopting project or standalone rigor- gem for a DSL, framework, or metaprogramming pattern.
Categories
Add or repair a read-only upstream submodule under references/. Rigor Add Reference is an agent skill from rigortype/rigor. Add or repair a read-only upstream submodule under references/.
Rigor Add Reference fits situations like: adding a reference checkout; diagnosing its clone; lifecycle failure; not for product code.
Run `npx skills add rigortype/rigor --skill rigor-add-reference -a claude-code`. Or copy the skill folder (.claude/skills/rigor-add-reference in rigortype/rigor) into .claude/skills/rigor-add-reference in your project. Claude Code loads it when a task matches its description.
Run `npx skills add rigortype/rigor --skill rigor-add-reference -a codex`. Or copy the skill folder (.claude/skills/rigor-add-reference in rigortype/rigor) into .agents/skills/rigor-add-reference in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rigortype/rigor --skill rigor-add-reference -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-add-reference, .gemini/skills/rigor-add-reference, .github/skills/rigor-add-reference and .opencode/skills/rigor-add-reference in your project.
Going by SKILL.md and its folder, Rigor Add Reference needs the command-line tools its instructions call (git, make, rg and nix). Our summary lists: Python 3.
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
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.
Rigor Add Reference is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Rigor Add Reference: Breaking Change Analysis (ruby-git/ruby-git, 1.8k stars), Gem Dependency Management (ruby-git/ruby-git, 1.8k stars), Ghostty Submodule and GhosttyKit Workflow (manaflow-ai/cmux, 28k stars) and GitVersion .NET Development (GitTools/GitVersion, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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 2, 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.