菜单
Test-first workflow and rules for fixing bugs in ruby-bindgen, including how to add coverage, the no-mocks policy, the no-Rice-workarounds policy, and where to put typedef-related test cases. Use whenever fixing a bug, adding a regression test, or before changing generator behavior.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run the ruby-bindgen test suites — all of them, or a single named test. Read-only — does not regenerate expected output. Use whenever you need to execute tests or check for regressions. To refresh golden files in test/bindings/cpp/, use the update-expected-output skill instead.
Regenerate the golden expected-output files under test/bindings/ by re-running the relevant tests with UPDATE_EXPECTED=1 (rice_test and cmake_test write to test/bindings/cpp/, ffi_test writes to test/bindings/c/). Use only after an intentional generator change, and only after the full test suite has been run to check for regressions. Never hand-edit files in test/bindings/.
| name | bug-fix-workflow |
| description | Test-first workflow and rules for fixing bugs in ruby-bindgen, including how to add coverage, the no-mocks policy, the no-Rice-workarounds policy, and where to put typedef-related test cases. Use whenever fixing a bug, adding a regression test, or before changing generator behavior. |
Every change to ruby-bindgen behavior follows the same loop: reproduce, cover, fix, verify.
Every bug fix MUST include test coverage. Write a failing test FIRST, then implement the fix.
test/headers/cpp/.Use test/headers/cpp/cross_file_base.hpp and
test/headers/cpp/cross_file_derived.hpp for any cross-file typedef
reproduction or regression test.
Do not batch multiple unrelated fixes into a single commit. Do not add
Co-Authored-By or any other author attribution to commit messages.