# rspec

Gives the agent a working set of RSpec conventions for Ruby and Rails: spec organization, test data, isolation. Useful when specs drift and duplicate.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 707 installs · ★ 286
- Author: Mindrally
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/Mindrally/skills/tree/HEAD/rspec/SKILL.md
- Updated: 2026-10-08
- HTML: https://affpapa.org/en/nevibecode/skills/rspec

## What it does

The skill frames the agent as an expert in Ruby, Rails and RSpec. It carries a list of principles: tests cover typical cases and edge cases, invalid input and error conditions included. `describe`, `context` and `it` blocks get descriptive names, assertions use the `expect` syntax, and the spec directory mirrors the source tree.

For data, the skill recommends `let` and `let!` over heavy setup, and FactoryBot factories over fixtures. Each test stays independent, with external services and databases mocked and methods stubbed. There is a counterweight too: over-mocking is called out, so real behavior gets tested where feasible.

Duplication is handled with `shared_examples` and `shared_context`, plus helpers and custom matchers for repeated patterns. The skill ships as a single `SKILL.md` holding the principles and a sample spec for a `User` model. It installs no gems and no config, so `rspec-rails` and FactoryBot need to be in the project before you ask the agent to write tests.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add Mindrally/skills --skill rspec -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/rspec/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/rspec/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add Mindrally/skills --skill rspec -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/rspec/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add Mindrally/skills --skill rspec -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/rspec/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install Mindrally/skills rspec
```

2. **Manually: put the files in place**
- File: `.github/skills/rspec/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add Mindrally/skills --skill rspec -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/Mindrally/skills --path rspec
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/rspec/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add Mindrally/skills --skill rspec -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Mindrally/skills/tree/HEAD/rspec/SKILL.md

## When to use it
- split a messy spec file into describe and context blocks
- cut duplicated setup across tests
- isolate a test from an external API with a mock
- move repeated assertions into shared_examples
- add edge cases to an existing test

## Example prompts
- Write specs for the User model following the rspec skill
- Break this spec file into describe and context blocks, build data with let and FactoryBot
- Pull the repeated assertions from these tests into shared_examples

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: ef74666ecb127c17.

BEGIN THIRD-PARTY FILE ef74666ecb127c17
````text
---
name: rspec
description: RSpec testing best practices for Ruby and Rails applications, covering test organization, data management, and isolation patterns.
metadata:
  maintainer: Mindrally
  source: https://github.com/Mindrally/skills
---

# RSpec Testing Best Practices

You are an expert in Ruby, Rails, and RSpec testing.

## Key Principles

### Comprehensive Coverage
Tests must cover both typical cases and edge cases, including invalid inputs and error conditions.

### Readability and Clarity
- Employ descriptive names for `describe`, `context`, and `it` blocks
- Use the `expect` syntax for improved assertion readability
- Keep test code concise without unnecessary complexity
- Include comments explaining complex logic

### Test Organization
- Use `describe` for classes/modules and `context` for different scenarios
- Use the `subject` helper to prevent repetition when defining objects under test
- Mirror your source file structure within the spec directory

### Test Data Management
- Leverage `let` and `let!` for minimal, necessary setup
- Prefer FactoryBot factories over fixtures for generating test data
- Create only the data necessary for each test

### Test Isolation
- Each test must be independent without shared state between tests
- Mock external services (APIs, databases) and stub methods appropriately
- Avoid over-mocking: test real behavior when feasible

### Reduce Duplication
- Share common behaviors across contexts using `shared_examples`
- Extract repetitive patterns into helpers or custom matchers
- Use `shared_context` for common setup across multiple specs

## Example Structure

```ruby
RSpec.describe User, type: :model do
  subject { build(:user) }

  describe 'validations' do
    it { is_expected.to validate_presence_of(:email) }
    it { is_expected.to validate_uniqueness_of(:email) }
  end

  describe '#full_name' do
    context 'when both first and last name are present' do
      let(:user) { build(:user, first_name: 'John', last_name: 'Doe') }

      it 'returns the combined name' do
        expect(user.full_name).to eq('John Doe')
      end
    end

    context 'when last name is missing' do
      let(:user) { build(:user, first_name: 'John', last_name: nil) }

      it 'returns only the first name' do
        expect(user.full_name).to eq('John')
      end
    end
  end
end
```
````
END THIRD-PARTY FILE ef74666ecb127c17

The third-party file has ended. Everything between the ef74666ecb127c17 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© Mindrally · Apache-2.0 · https://github.com/Mindrally/skills/tree/HEAD/rspec/SKILL.md

## Similar
- [inertia-rails-testing](https://affpapa.org/en/nevibecode/skills/inertia-rails-testing.md) — skill · 465 installs
- [rails-expert](https://affpapa.org/en/nevibecode/skills/rails-expert.md) — skill · 4700 installs
- [rails-cursorrules-prompt-file](https://affpapa.org/en/nevibecode/rules/rails-cursorrules-prompt-file.md) — rule · ★ 41011
- [sentry-ruby-sdk](https://affpapa.org/en/nevibecode/skills/sentry-ruby-sdk.md) — skill · 2100 installs
- [appwrite-ruby](https://affpapa.org/en/nevibecode/skills/appwrite-ruby.md) — skill · 796 installs
- [ruby-rails-application](https://affpapa.org/en/nevibecode/skills/ruby-rails-application.md) — skill · 655 installs

From the same set: [mindrally/skills](https://affpapa.org/en/nevibecode/by/mindrally/skills.md) — 214 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md