ruby
Skill17 starsChanged 50 days agoMITView on GitHub
Ruby gem development with modern tooling, testing, and publishing. Use when working with .gemspec, Rakefile, or user asks about gem structure, RSpec for gems, Bundler, or gem publishing. Not for Rails apps (use rails skill).
11 other projects use a version of this.
Adopted by
Most recently taken up by
- rogue-dev-studio/ai-agents-roguetheir own version, first seen Nov 1, 2026
- damacus/agent-skillstheir own version, first seen Oct 29, 2026
- bsene/skillstheir own version, first seen Oct 25, 2026
- mukco/claude-skillstheir own version, first seen Oct 15, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
Used with
Projects with it also use grill-me.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- carapace-sh/carapace-bin★ 2ksame name
- Mindrally/skills★ 275same name
- nimadorostkar/Claude-Skills-collection★ 33same name
- G1Joshi/Agent-Skills★ 15same name
- bsene/skills★ 7same name
- damacus/agent-skills★ 2same name
- display-design-studio/skills★ 2same name
- kimtth/agent-skill-100-lines-or-less★ 2same name
- rogue-dev-studio/ai-agents-rogue★ 2same name
- martinstreicher/claude-skills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- adrSkill
- android-kotlinSkill
- apple-swiftSkill
- autoresearch-promptSkill
- blog-writerSkill
- cloud-infrastructureSkill
- commitSkill
- cover-imageSkill
- freezeSkill
- gemini-reviewSkill
- golangSkill
- harness-mechanicSkill
- harness-traceSkill
- humanizerSkill
- ios-debuggerSkill
- knowledge-syncSkill
- learning-docsSkill
- learning-loopSkill
- obsidianSkill
- orchestratorSkill
- plan-forgeSkill
- process-clippingsSkill
- project-analyzerSkill
- project-checksSkill
- pr-reviewSkill
- pythonSkill
- railsSkill
- react-nextjsSkill
- refine-requirementsSkill
- releasing-softwareSkill
- scoreSkill
- second-opinionSkill
- skill-forgeSkill
- source-controlSkill
- terraformSkill
- test-design-reviewerSkill
- verify-frontendSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 36
Read .ruby-version / Gemfile / <gem>.gemspec (required_ruby_version) for the project's floor.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ABOUTME: Ruby gem development guide - structure, testing, linting, CI/CD, publishing
ABOUTME: Conventions for gemspec, RSpec, RuboCop, publishing with attestation
Ruby Gem Development
Quick Reference
bundle gem my_gem --test=rspec --ci=github --linter=rubocop
bundle install && bundle exec rspec && bundle exec rubocop -A
gem build my_gem.gemspec
gem push my_gem-1.0.0.gem --attestationFor Rails apps, use rails skill. See also: _AST_GREP.md, _PATTERNS.md, source-control
Version (determine, don't assume)
See ../_LANG_COMMON.md. Fetch the truth:
ruby -v # local interpreter
cat .ruby-version 2>/dev/null # pin file (if present)
curl -s https://endoflife.date/api/ruby.json | jq -r '.[0].latest' # latest upstream stableRead .ruby-version / Gemfile / <gem>.gemspec (required_ruby_version) for the project's floor.
Pre-Commit Verification (MANDATORY)
make check && make test-e2e must pass (enforced by the pre-commit-gate hook; see ../_LANG_COMMON.md). What make check expands to for a gem:
bundle exec rubocop
bundle exec rspec
bundle exec bundler-audit check --updateGem Structure
my_gem/
├── lib/my_gem.rb # Entry point
├── lib/my_gem/version.rb # VERSION constant
├── spec/ # RSpec tests
├── sig/ # RBS types (optional)
├── .github/workflows/ci.yml
├── .rubocop.yml
├── my_gem.gemspec
└── GemfileEntry Point (lib/my_gem.rb)
# frozen_string_literal: true
# ABOUTME: Main entry point for MyGem
# ABOUTME: Requires all components and provides configuration
require_relative "my_gem/version"
require_relative "my_gem/client"
module MyGem
class << self
attr_writer :configuration
def configuration = @configuration ||= Configuration.new
def configure = yield(configuration) if block_given?
end
endGemspec
# frozen_string_literal: true
Gem::Specification.new do |spec|
spec.name = "my_gem"
spec.version = MyGem::VERSION
spec.required_ruby_version = ">= <current stable minus one>" # Always specify! Check `ruby -v` / endoflife.date, do not hardcode from memory
spec.metadata = {
"rubygems_mfa_required" => "true", # Required!
"source_code_uri" => "https://github.com/you/my_gem",
"changelog_uri" => "https://github.com/you/my_gem/blob/main/CHANGELOG.md"
}
spec.files = Dir.glob(%w[lib/**/* LICENSE.txt README.md CHANGELOG.md])
# Runtime deps in gemspec, dev deps in Gemfile
endTesting & Quality
RSpec: describe/it with expect syntax, subject(:name), WebMock for HTTP, SimpleCov >= 90%.
RuboCop: rubocop-rspec + rubocop-performance, TargetRubyVersion set to the gem's required_ruby_version floor (do not hardcode from memory), NewCops: enable, max line 120, max method 10.
Thread safety: Mutex.new + @mutex.synchronize { ... } for shared state.
For detailed testing examples, CI config, HTTP client pattern, and publishing steps, see references/ruby-patterns.md.
Code Review Checklist
| Category | Checks |
| Structure | frozen_string_literal, ABOUTME headers, standard layout |
| Gemspec | required_ruby_version, rubygems_mfa_required, metadata URIs |
| Testing | RSpec expect syntax, SimpleCov >= 90%, WebMock, no real HTTP |
| Quality | RuboCop passes, thread-safe if async, custom error classes |
| CI | Matrix on the two latest stable Ruby minors (check endoflife.date, do not hardcode), ruby/setup-ruby, bundler-cache |
Resources
- Bundler: Creating Gems
- RubyGems Patterns
- Ruby version changes (pick the entry for the project's Ruby version)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

