forgecad-inspect-model

Inspect Model

Use forgecad inspect ... when a shaded render is too ambiguous and you need structured evidence: a bundle directory with evidence PNGs plus a root manifest.json (or, for inspect section, a probe directory with result.json, section.svg, section.png). Inspection is not a substitute artifact: look inside with sections, masks, --focus/--hide, and transparency — never edit the model into a cutaway or exploded default to make inspecting easier. Output dirs: let inspect allocate its timestamped directory by default (repeated probes never collide); use /tmp/<model>-inspect for throwaway bundles, a project directory only for persistent artifacts.

Routing: authoring/API questions → forgecad skill; creating a new model → forgecad-build-model.

Workflow

1. Identify the failure question. What would make the model wrong: overlap, thin walls, hidden cavity failure, disconnected or accidentally fused bodies, floating parts, orientation artifacts, identity confusion?

2. Confirm the model executes. If in doubt, run forgecad run model.forge.js first; add --debug-imports for suspect imports.

3. Pick ONE targeted evidence command from the table below. forgecad inspect evidence lists everything available.

4. Summarize the manifest first, then use jq against manifest.json for targeted follow-up. The helper ships beside this SKILL.md — invoke it skill-dir-relative; it accepts the bundle directory or a manifest.json path:

   python <this-skill-dir>/summarize_manifest.py /tmp/model-inspect
   

5. Inspect the PNGs, not only the JSON. View identity/context images first, then the risk evidence's view, then orthogonal cameras (front, right, top) when iso hides the issue, sections only when internals matter. In automation, resolve file paths through the manifest — custom cameras break canonical filenames.

6. Isolate intentional overlaps with --focus "A,B" or --hide "C" so the remaining report stays meaningful.

7. Treat findings as model bugs: unexpected collisions, critical thin regions, high unresolved thickness area, wrong component counts, floating bodies, or surprising gaps mean fix the model and reinspect.

8. Report honestly. Include the exact command, bundle path, manifest highlights, and the PNG views actually inspected. Never claim geometry is verified if you only ran forgecad run.