igmarin/rails-tdd-loop
skills/workflows/rails-tdd-loop/SKILL.md
Orchestrates the full Rails test-driven development cycle: generates a failing spec first, implements minimal code to pass, refactors, then produces YARD documentation and a self-reviewed PR. Use when practicing test-driven development, red-green-refactor, TDD workflow, writing tests before code, adding tests first, or building a Rails feature where specs must gate implementation.
$ install --global
skillsauthnpx skillsauth add igmarin/rails-agent-skills rails-tdd-loopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 4, 2026, 2:45 AM46.3s2 files scanned
SKILL.md
- name:
- rails-tdd-loop
- license:
- MIT
- description:
- >
- Orchestrates the full Rails test-driven development cycle:
- generates a failing spec first, implements minimal code to pass, refactors, then produces YARD documentation and a self-reviewed PR. Use when practicing test-driven development, red-green-refactor, TDD workflow, writing tests before code, adding tests first, or building a Rails feature where specs must gate implementation.
- version:
- 1.0.0
- keywords:
- rails, tdd, workflow, feature, implementation, testing, orchestration
Rails TDD Loop — Complete Feature Workflow
Workflow Phases
Phase 1: Context & Test Design
- skills/context/rails-context-engineering — Load schema, routes, nearest patterns (ensures context matches codebase)
- skills/testing/rails-tdd-slices — Choose the correct first failing spec (model→model spec, API→request, UI+DB→system)
- skills/testing/rspec-best-practices — Write the test and verify it FAILS (use
let/build, confirm failure is for missing feature)
HARD GATE — Test Feedback Checkpoint:
- Test EXISTS (written and saved)
- Test has been RUN
- Test FAILS for the correct reason (feature missing, not typo/config)
| Failure type | Example | Action |
|-------------|---------|--------|
| Correct | undefined method 'full_name' | Proceed to implementation |
| Incorrect | syntax error, factory not registered | Return to rspec-best-practices |
If test feedback is NOT OK: Return to rspec-best-practices and refine.
Phase 2: Implementation
-
Implementation Proposal Checkpoint — Propose approach (example: "User#full_name: concatenate first_name + last_name with space")
-
User confirms approach — Wait for explicit approval
-
Implement minimal code to pass the test (single method, no premature abstractions, simplest thing that works)
-
Verify test passes — Run the spec again:
bundle exec rspec spec/path/to/your_spec.rb
If test does NOT pass: Return to implementation (minimal changes, re-verify).
Phase 3: Iterate (Optional)
Check: More behaviors to implement?
- Yes: Return to Phase 1 (rspec-best-practices) for next behavior
- No: Proceed to Phase 4
Phase 4: Finish
- Linters + Full Test Suite:
bundle exec rubocop bundle exec brakeman --no-pager bundle exec rspec - skills/patterns/yard-documentation — Document public Ruby API (code documentation)
- skills/code-quality/rails-code-review — Self-review the PR (quality assurance)
- Open PR — Feature complete
Integration
Workflow complete → PR ready. Bug mid-implementation → skills/testing/rails-bug-triage. Security/architecture concerns → skills/code-quality/rails-security-review / skills/code-quality/rails-architecture-review.
Example
Inline example with file structure:
spec/models/user_spec.rb:
RSpec.describe User do
describe '#full_name' do
let(:user) { build(:user, first_name: 'John', last_name: 'Doe') }
it 'concatenates first and last name' do
expect(user.full_name).to eq('John Doe')
end
end
end
app/models/user.rb:
def full_name
"#{first_name} #{last_name}"
end
See assets/example.md for complete end-to-end walkthrough with commands and phases.
Related Skills
igmarin/rails-agent-skills
development
VerifiedTrustedCommunity
Entry point for Rails development workflows covering TDD, RSpec, Service Objects, DDD, GraphQL, Engines, and Code Quality. Use when the user asks about Ruby on Rails development patterns, needs RSpec test suites generated, wants service objects scaffolded, is setting up GraphQL schemas, performing Rails code review, refactoring .rb files, working with domain-driven design, implementing background jobs, conducting Rails security checks, or building Rails engines. Generates RSpec tests, structures service objects, enforces TDD workflows, configures GraphQL schemas, and coordinates domain-driven design patterns. Trigger keywords: Rails, RSpec, TDD, Rails testing, Rails refactor, Rails API, Rails code review, domain driven design, service objects, GraphQL, Rails engine, Ruby, .rb, background jobs, Rails migrations, Rails security check.
21SKILL.mdUpdated May 18, 2026
igmarin/release-engine
development
VerifiedTrustedCommunity
Use when shipping a Rails engine gem — FIRST run full test suite (`bundle exec rspec`) and fix ALL failures, verify gemspec metadata and dependencies match tested Rails/Ruby versions, dry-run: `gem build *.gemspec && gem push --dry-run *.gem` and verify contents, generate CHANGELOG.md organized by category (added/changed/deprecated/removed/fixed), produce step-by-step upgrade notes with before/after code, set semantic version in `lib/[engine_name]/version.rb`, document deprecations with migration paths, load release assets conditionally and state which one informed the output. Trigger words: version bump, changelog, deprecation, gemspec, upgrade, release, publish gem, ship gem.
21SKILL.mdUpdated May 9, 2026
igmarin/tdd
development
VerifiedTrustedCommunity
Orchestrates the full Rails TDD cycle with hard gates: test MUST exist, be run, and FAIL for the correct reason (e.g. undefined method, not syntax error) before any implementation code — propose minimal implementation and wait for user approval → verify test PASSES → run full suite with rubocop, brakeman, rspec all green → produce YARD documentation and self-reviewed PR; phases context/test design→implementation→iterate→finish. Use when practicing test-driven development, red-green-refactor, TDD workflow, writing tests before code, adding tests first, or building a Rails feature where specs must gate implementation.
19SKILL.mdUpdated Jun 5, 2026
igmarin/setup
development
VerifiedTrustedCommunity
Complete Rails project setup loop with hard gates: verify Ruby version matches .ruby-version, Bundler installed, database connection successful, all env vars loaded, and ALL external CI actions pinned to immutable commit SHAs (never mutable tags like @v4) → configure CI/CD pipeline with linting, testing, and security scanning → validate end-to-end with bundle install, db:create, db:migrate, rspec, and write SETUP_CHECKLIST.md; phases context/onboarding→CI/CD configuration→environment validation. Use when starting a new Rails project, running `rails new`, configuring a Gemfile or .ruby-version, setting up a development environment, or wiring up CI/CD for a Ruby on Rails app. Trigger: setup project, new Rails app, configure CI/CD, dev environment setup, rails new, Gemfile setup, .ruby-version, Ruby on Rails project bootstrap.
19SKILL.mdUpdated Jun 5, 2026