메뉴
Run Rubyzen's unit test suite. Use this skill when the user wants to run tests, verify changes, check if an API is broken, or confirm that specs pass. Also trigger when the user says "run specs", "run the tests", "does it pass?", or "check the tests".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Write unit tests for Rubyzen's own API components — declarations, providers, collections, RSpec matchers, or Minitest assertions. Use this skill when the user wants to add tests for an existing or newly added Rubyzen component, increase test coverage, or write specs for untested methods. Also trigger when the user says "test this declaration", "add specs for", or "write tests for the X collection".
Add a new code concept to Rubyzen — a new Declaration, Provider, and Collection as a full vertical slice. Use this skill whenever the user wants to add support for a new Ruby language construct (e.g., case statements, loops, yield calls, begin/end blocks, lambda expressions), add a new API to the library, or extend Rubyzen's analysis capabilities. Also use when the user says "add support for X" or "I want to lint on X" where X is a code structure not yet modeled.
Run the sample project lint rules to verify that Rubyzen detects architectural violations. Use this skill when the user wants to run lint rules, verify that violations are detected, or test that a new lint rule works. Also trigger when the user says "run the lint rule", "check violations", or "test the sample project".
Write an architectural lint rule for a Ruby project using the Rubyzen API. Use this skill when the user wants to create a new lint rule, enforce an architectural constraint, add a code quality check, or write an RSpec or Minitest test that validates code structure. Also trigger when the user says things like "controllers shouldn't do X", "models must always Y", "enforce that Z", or "add a rule for".
| name | run-tests |
| description | Run Rubyzen's unit test suite. Use this skill when the user wants to run tests, verify changes, check if an API is broken, or confirm that specs pass. Also trigger when the user says "run specs", "run the tests", "does it pass?", or "check the tests". |
Unit tests verify the correctness of Rubyzen's own API — declarations, providers, collections, RSpec matchers, and Minitest assertions. Rubyzen has two test suites: RSpec specs in spec/ and Minitest tests in test/.
# Both suites (RSpec then Minitest)
bundle exec rake
# RSpec only
bundle exec rspec spec
# Minitest only
bundle exec rake test
bundle exec rspec spec/declarations/class_declaration_spec.rb
# All declaration tests
bundle exec rspec spec/declarations/
# All collection tests
bundle exec rspec spec/collections/
# All matcher tests
bundle exec rspec spec/matchers/
# All provider tests (covered within declaration specs)
bundle exec rspec spec/declarations/
spec/
├── spec_helper.rb # Loads Rubyzen, includes parse helper
├── support/
│ └── parse_helper.rb # parse_ruby helper for inline snippets
├── fixtures/ # Small .rb files for Project path tests
├── declarations/ # One spec per declaration type
├── collections/ # One spec per collection type
├── matchers/ # One spec per matcher
├── project_spec.rb # Project class tests
└── cache/
└── parse_cache_spec.rb # Caching behavior tests
test/
├── test_helper.rb # Loads rubyzen/minitest + parse helper
├── assertions/
│ └── zen_assertions_test.rb # assert_zen_empty / _true / _false
└── minitest_adapter_test.rb # Entry-point contract test
zen_empty, zen_true, zen_false)