verify

Interprets CubiC? No, interprets Brep CLI JSON reports to identify CAD geometry errors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually checking brepjs CAD part validity is error-prone: visual renders only confirm shape, not correctness, and raw JSON reports are hard to interpret without context. This skill eliminates that guesswork by guiding you through the full verification and repair workflow.

Core Features & Use Cases

  • Structured Report Interpretation: Parses the brep CLI JSON report to clearly distinguish between broken geometry (failed validity checks) and valid but dimensionally incorrect geometry (failed assertions).
  • Targeted Repair Guidance: Uses error codes and hints to localize issues to the smallest responsible code section, avoiding full part rewrites.
  • Use Case: You have a machined bracket part that fails validation. Use this skill to read the report, identify the invalid fillet radius error, adjust only that section of code, and re-verify until the part passes all checks.

Quick Start

Use the verify skill to check the validity of your attached brepjs CAD part file, interpret its verification report, and guide you through fixing any reported errors step by step.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I validate brepjs CAD parts and interpret geometry verification reports?

Validate brepjs CAD parts by parsing structured CLI JSON verification reports to distinguish broken geometry from dimensionally incorrect valid geometry, mapping error codes to actionable repair steps for manufacturable solid modeling.

Why does my parametric CAD part render correctly but fail solid modeling validation?

Visual renders only confirm shape, not correctness. Parametric CAD parts can fail validation due to broken geometry failing validity checks or dimensionally incorrect geometry failing assertions, requiring structured report interpretation to identify.

How do I fix geometry errors in brepjs without rewriting the entire parametric part?

Fix geometry errors by using CLI verification error codes and hints to localize issues to the smallest responsible code section, adjusting only that specific section, and re-verifying incrementally until all checks pass.

What is the difference between broken geometry and valid but dimensionally incorrect geometry in CAD verification?

Broken geometry fails validity checks indicating structural solid modeling errors, while valid but dimensionally incorrect geometry passes structural checks but fails assertions, meaning the shape is valid but does not match intended parametric dimensions.

Can I use CLI JSON validation reports to debug code-first CAD workflows for manufacturable solid geometry?

Yes, CLI JSON validation reports support code-first CAD workflows by providing structured outputs that enforce disciplined incremental debugging, allowing you to parse errors and iterate on parametric parts until achieving manufacturable solid geometry.

What's the best way to troubleshoot an invalid fillet radius error in a machined bracket part?

Troubleshoot invalid fillet radius errors by reading the CLI JSON verification report, identifying the specific error code, adjusting only the responsible code section with the incorrect fillet radius, and re-verifying the machined bracket until it passes.