omnidist

Expert guidance for bootstrapping and running @omnidist/omnidist in a Go repository.

When to trigger

• The user mentions omnidist or asks for omnidist init, omnidist ci, or release pipeline setup.
• The task involves distributing Go binaries through npm and/or uv (PyPI-style index).
• The user needs generated release workflow files for GitHub Actions.

Core rules

• Run commands from the repository root.
• Use npx -y @omnidist/omnidist@latest for all omnidist commands to avoid stale versions and global install assumptions.
• Treat generated files as templates: review and customize before committing.
• Before generating CI, set tool.main to the project's real command path (for example ./cmd/<project-binary>), never leave ./cmd/omnidist unless that is truly the project command.
• Before generating CI, set distribution package names to the project's real packages:
  • distributions.npm.package must match the intended npm scoped package (for example @org/project).
  • distributions.uv.package must match the intended uv/PyPI package name.
• Do not keep omnidist defaults for package names when they do not match the project.