debugging-doctrine

Diagnose and resolve complex geometry bugs in the brepkit library.

20|3|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/andymai/brepkit --skill debugging-doctrine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-doctrine
Source: https://github.com/andymai/brepkit/tree/main/.claude/skills/debugging-doctrine
Command: npx skills add https://github.com/andymai/brepkit --skill debugging-doctrine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a systematic approach to debug complex geometry bugs in the brepkit library, ensuring accurate diagnosis and resolution of issues that affect boolean operations, fillet, offset, and tessellation.

Core Features & Use Cases

  • Systematic Debugging Methodology: A structured process to investigate and resolve bugs effectively.
  • Detailed Repro Guidelines: Step-by-step instructions to create accurate reproductions of bugs.
  • Instrumentation and Analysis: Tools and techniques for inspecting the state of the geometry and operations.
  • Use Case: When a boolean operation produces incorrect volume or face count, this Skill offers a clear path to diagnose and fix the problem.

Quick Start

Run the debugging-doctrine skill with your specific geometry files and observe the step-by-step guidance for debugging.

Frequently Asked Questions about debugging-doctrine

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

FAQPage Schema
How do I debug incorrect volume or face count from boolean operations in brepkit?

To debug boolean operation errors in brepkit, use a systematic debugging methodology with detailed repro guidelines and instrumentation tools to inspect geometry state and diagnose the root cause efficiently.

What's the best way to create a repro for geometry bugs affecting fillet and offset operations?

The best way to create a repro for fillet and offset geometry bugs is to follow structured step-by-step repro guidelines that accurately recreate the issue, enabling precise inspection of the geometry state.

Why does tessellation in brepkit produce incorrect output and how can I investigate?

Tessellation in brepkit produces incorrect output due to complex geometry bugs that you can investigate using detailed analysis tools and instrumentation techniques to inspect the state of operations.

Can I use this debugging methodology for any geometry library or is it specific to brepkit?

This debugging methodology is specifically designed to diagnose and resolve complex geometry bugs within the brepkit library, focusing on boolean operations, fillet, offset, and tessellation issues.

What steps should I follow to diagnose complex geometry bugs systematically?

To diagnose complex geometry bugs systematically, follow a structured debugging process that includes creating accurate reproductions, instrumenting the code, and inspecting the geometry and operation states.