debugging-geometry

Triage brepjs geometry failures by symptom class and validate numeric sanity.

77|7|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/andymai/brepjs --skill debugging-geometry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-geometry
Source: https://github.com/andymai/brepjs/tree/main/.claude/skills/debugging-geometry
Command: npx skills add https://github.com/andymai/brepjs --skill debugging-geometry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork when debugging brepjs geometry failures, from invalid boolean results and empty degenerate shapes to STEP export crashes and cross-kernel divergences, cutting down hours of trial-and-error CAD debugging.

Core Features & Use Cases

  • Failure Triage: Quickly categorize geometry issues (error results, bad geometry, degenerate shapes, kernel traps, kernel divergences) to jump straight to the relevant fix path.
  • Numeric & Healing Guidance: Validate geometry with measurement checks, navigate the autoHeal pipeline correctly (avoiding the common short-circuit trap where healing passes never run), and escalate repairs appropriately.
  • Boolean & Export Debugging: Diagnose boolean failure root causes (including the notorious #1126 disjoint-fuse corruption that causes silent STEP export crashes) and use the brep CLI for visual debugging and shape comparison.
  • Use Case: If your brepjs boolean operation returns an Err, your exported STEP file triggers a WebAssembly.RuntimeError, or your part renders incorrectly, this Skill walks you through the exact steps to isolate and fix the issue.

Quick Start

Use the debugging-geometry skill to follow the step-by-step playbook to isolate and fix your brepjs geometry failure, starting with triaging the error class and running numeric sanity checks on your shape.

Frequently Asked Questions about debugging-geometry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix invalid boolean operation results in brepjs?

To fix invalid boolean operation results in brepjs, follow a symptom-ordered triage playbook that categorizes the geometry failure and runs numeric sanity checks to isolate the root cause before applying targeted repairs.

Why does my STEP export crash with a WebAssembly.RuntimeError?

A STEP export crash with a WebAssembly.RuntimeError is often caused by the disjoint-fuse corruption issue #1126, which requires diagnosing the boolean failure root cause and validating the shape before exporting.

How does the brepjs autoHeal pipeline work for degenerate shapes?

The brepjs autoHeal pipeline works by escalating repairs for degenerate shapes, but you must navigate it correctly to avoid the common short-circuit trap where healing passes never actually run.

Can I use the brep CLI for visual debugging of geometry errors?

Yes, you can use the brep CLI for visual debugging of geometry errors by visually inspecting and comparing shapes to identify invalid boolean results and empty degenerate shapes.

What is the best way to isolate cross-kernel divergence between occt-wasm and manifold?

The best way to isolate cross-kernel divergence between occt-wasm and manifold is to use a kernel divergence isolation workflow that runs numeric sanity validation and compares shape outputs across the kernels.

What are the common limitations when debugging brepjs geometry failures?

Limitations when debugging brepjs geometry failures include navigating the autoHeal pipeline short-circuit trap where healing passes never run, and addressing silent STEP export crashes caused by disjoint-fuse corruption.