test
Skill93 starsChanged 8 days agoMITView on GitHub
Run RSpec tests — full suite, quick, system, or specific files
179 other projects use a version of this.
Adopted by
Most recently taken up by
- tyrantpiper/travel-pwatheir own version, first seen Nov 8, 2026
- phuthuycoding/kanban-flowtheir own version, first seen Nov 8, 2026
- pche-broken-artist/forge-of-thoughttheir own version, first seen Nov 8, 2026
- PMDevSolutions/Flaviantheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.
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.
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
parcadeiSkillagentica-infrastructure
Reference guide for Agentica multi-agent infrastructure APIs
Also in 3 projects that use this
- +10 more from parcadei
Other versions179 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 179
- react/react★ 252ksame name
- facebook/react★ 252ksame name
- apache/skywalking★ 25ksame name
- livewire/livewire★ 24ksame name
- NVIDIA/TensorRT★ 13ksame name
- FalkorDB/FalkorDB★ 10ksame name
- FastLED/FastLED★ 7.5ksame name
- fleetdm/fleet★ 7.2ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
169 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 repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-breadcrumb-pageSkill
- chaosSkill
- cqrs-patternsSkill
- demo-updateSkill
- host-app-safetySkill
- new-featureSkill
- release-rulesSkill
- releaseSkill
- roadmap-statusSkill
- safety-checkSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 154 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Run the RSpec test suite with various scopes.
- Distinctive: line 54
If failures occur, read the failure output and suggest fixes
- Distinctive: line 55
If all pass, report the count and time
“Common” is measured: kept by at least 6 in 10 of the 154 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
/test — Run RSpec Tests
Run the RSpec test suite with various scopes.
Usage
/testor/test all— full suite (~1895 specs, ~37s)/test quick— skip system tests (faster)/test system— system tests only (Capybara + Cuprite, headless Chrome)/test system visible— system tests with visible browser (HEADLESS=false)/test <path>— specific file or directory (e.g.,/test spec/queries/)
Commands
Full Suite
bundle exec rspecQuick (Skip System Tests)
bundle exec rspec --exclude-pattern "spec/system/**/*_spec.rb"System Tests
bundle exec rspec spec/system/Visible Browser
HEADLESS=false bundle exec rspec spec/system/With Inspector (Chrome DevTools)
INSPECTOR=true HEADLESS=false bundle exec rspec spec/system/Specific File
bundle exec rspec spec/queries/rails_error_dashboard/errors_list_spec.rbAfter Running
- Report the result summary (examples, failures, pending)
- If failures occur, read the failure output and suggest fixes
- If all pass, report the count and time
Test Organization
spec/
├── commands/ # Command specs (writes)
├── queries/ # Query specs (reads)
├── services/ # Service specs (algorithms)
├── models/ # Model specs
├── jobs/ # Job specs
├── helpers/ # Helper specs
├── generators/ # Generator specs
├── integration/ # Cross-layer tests
├── system/ # Capybara browser tests (6 specs)
├── support/ # Shared helpers, factories, config
└── dummy/ # Test Rails appNotes
- System tests use Cuprite (Chrome DevTools Protocol, not Selenium)
- WebMock allows CDN requests in system specs only
- Auth in system tests: URL-embedded HTTP Basic Auth via
visit_dashboardhelper - Ruby 4.0.1:
ostructremoved from default gems — test factory usesStructinstead
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.

