DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to ship a PartMode CAD fix that passes the contributor gate with Partmode

Run the focused gate and the affected smoke checks before submitting a behavior change.

Authorization notice. Partmode is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forAn open-source contributor who has been assigned an issue on a CAD feature, assembly, drawing, or agent path.

The problemCAD changes need exact kernel evidence, not screenshots alone, so a fix needs the right regression checks before it is reviewed.

The outcomeA pull request backed by a passing `npm run ci:gate` and the named smoke checks, with the settled document result reported.

What you need first

  • Node.js 22.13 or newer
  • git and npm available in a terminal
  • A PartMode account and a revocable agent key, only for hosted agent access
  • Validation of dimensions, tolerances, and materials for any real manufacturing use

Steps

  1. Comment on the GitHub issue before starting so scope and ownership are clear.
  2. Run npm ci, then npm run build, and add or update the narrowest relevant regression.
  3. Run npm run ci:gate.
  4. Run each affected smoke:* command named by the issue, such as smoke:brep-evidence for exact geometry changes.
  5. Report the settled document result and the kernel, B-rep, topology, or export evidence in the pull request.

Prompt for your agent

In the BOMWiki/partmode repository, make the change described in issue <issue-number> within its accepted boundary, run `npm run ci:gate`, and run the affected smoke checks listed in the issue. Report the gate result and the exact kernel or export evidence, and verify that the gate exits with status 0 before opening a pull request.

Caveat. Screenshots and mesh counts are only supporting evidence, so the pull request must report exact kernel, B-rep, topology, or export results.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page