Skip to content

ericrisco/rsc-harness / skills/ruby

Use when writing or refactoring plain Ruby outside Rails — scripts, CLIs, gems, libraries: Enumerable chains and blocks, module mixins and value objects, Bundler/gemspec packaging, whether metaprogramming earns its keep, Minitest or RSpec, Ruby 3.4/4.0 frozen-string hygiene. NOT Rails, ActiveRecord, or ActiveSupport idioms (that is `rails`).

FileKindSize
SKILL.mdskill md12.5 KB
evals/README.mdmarkdown878 B
evals/cases.yamlconfig2.8 KB
references/gems-and-testing.mdmarkdown5.3 KB
references/metaprogramming.mdmarkdown5.2 KB
scripts/verify.shexecutablescript2.5 KB

evals/README.md

View on GitHub
# Evals for the `ruby` skill

`cases.yaml` holds three kinds of fixture. `should_trigger` lists prompts whose
situation this skill should claim (idiomatic plain-Ruby work — Enumerable refactors,
gem packaging, metaprogramming judgment, Minitest/RSpec, the FrozenError-after-upgrade
case, plus a Catalan phrasing). `should_not_trigger` lists adjacent prompts that must
route to a real sibling instead (`rails`, `python`, `elixir`, `github-actions`), each
with the reason. The single `capability` case is a build-a-gem scenario scored against
a `must_include` rubric. Run them with the repository's eval harness over `evals/`,
which matches the trigger/route fixtures against the skill description and checks a
capability transcript against the rubric. No network or Ruby toolchain is required to
score the routing cases; the capability rubric is judged on the produced answer.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall