Author and debug cross-kernel tests for the brepjs CAD JavaScript library.
npx skills add https://github.com/andymai/brepjs --skill writing-tests-andymai
Please help me install this Agent Skill. Skill: writing-tests Source: https://github.com/andymai/brepjs/tree/main/.claude/skills/writing-tests Command: npx skills add https://github.com/andymai/brepjs --skill writing-tests-andymai
The brepjs CAD library supports four distinct geometry kernels, each with unique behavioral quirks, strict code coverage thresholds, and complex CI/pre-commit quality gates. Writing tests that run reliably across all kernels, meet coverage requirements, and avoid common flakiness is time-consuming and error-prone without explicit, repository-specific guidance. This skill eliminates that friction by providing end-to-end instructions for the entire brepjs testing workflow.
Use the writing-tests skill to add a cross-kernel regression test for the new chamfer operation you just merged into brepjs, ensuring it passes the occt-wasm default gate and meets coverage requirements.
High-intent search queries and answers about installing and using this skill.
To write cross-kernel tests for brepjs, use kernel-portable test skeletons and handle kernel-specific behavioral divergences via the official registry. This ensures your tests run reliably across all supported geometry kernels without flakiness.
Bare vitest runs fan out to all kernel projects because they lack specific project targeting. You must use the correct configuration to isolate runs to a single kernel, such as the occt-wasm default gate, preventing unintended cross-kernel execution.
To meet strict code coverage thresholds for new brepjs operations, follow the end-to-end testing workflow to verify your tests hit the required coverage floor. This helps you pass pre-commit and CI checks without unnecessarily lowering thresholds.
Handling kernel-specific numeric tolerances in brepjs CAD tests requires using the official registry to manage behavioral divergences. This approach allows you to account for capability gaps and tolerance differences across distinct geometry kernels.
You can detect performance regressions when adding new chamfer or fillet operations by running stress and benchmark suites. Interpreting these regression results catches slowdowns early and confirms your new operation meets performance standards.
Troubleshooting failing cross-kernel regression tests in brepjs involves debugging through the multi-kernel test execution workflow. This process identifies whether failures stem from kernel-specific behavioral divergences or numeric tolerance mismatches.
andymaiImplement cross-kernel geometry methods across brepjs CAD kernels.
Sheldon-92Execute test suites and report failures with coverage metrics.
luongnv89Automate pre-commit hooks and GitHub Actions for code quality.
andymaiDetect and resolve floating-point issues in CAD kernel operations.
