Align local Mojo builds with CI using pixi shell-hook and zero-warnings policy.
npx skills add https://github.com/mvillmow/ml-odyssey --skill build-run-local
Please help me install this Agent Skill. Skill: build-run-local Source: https://github.com/mvillmow/ml-odyssey/tree/main/.claude/skills/build-run-local Command: npx skills add https://github.com/mvillmow/ml-odyssey --skill build-run-local
This Skill helps you run local builds in an environment that mirrors CI, enabling you to validate changes before pushing.
Activate environment: eval $(pixi shell-hook) Verify mojo version: pixi run mojo --version Build project: pixi run mojo build -I . shared/core/extensor.mojo Run tests: pixi run mojo test -I . tests/shared/core/ Run a specific test: pixi run mojo test -I . tests/shared/core/test_extensor.mojo Format code: pixi run mojo format .
High-intent search queries and answers about installing and using this skill.
Local builds mirror CI by activating the pixi environment with eval $(pixi shell-hook), which sets MOJO_PATH and required flags. Build using pixi run mojo build -I . -O --no-warn-unused to compile with proper include paths and enforce zero-warnings policy.
Execute tests locally using pixi run mojo test -I . -v -k pattern to run test suites with verbose output and pattern matching. Run specific test files with pixi run mojo test -I . tests/shared/core/test_extensor.mojo to verify behavior matches CI.
Local build failures typically stem from environment misalignment. Ensure pixi shell-hook is activated, MOJO_PATH is configured correctly, and you're building with -I . -O --no-warn-unused flags to replicate CI's strict zero-warnings policy.
Prerequisites include pixi for environment management and Mojo installed within the pixi environment. Activate with eval $(pixi shell-hook), verify the version with pixi run mojo --version, then configure include paths with -I . for local builds and tests.
Yes. Run pixi run mojo format . to format code locally, then execute builds and tests with zero-warnings enforcement using -O --no-warn-unused flags to catch issues before pushing to CI.
Yes. Use -I . to include the local directory, -O for optimization, --no-warn-unused to enforce zero-warnings policy, and -v for verbose test output. These flags align local builds and tests with CI configuration.
bughqManage system-level dependencies and workspace configurations in Stacks projects.
HaykTarkhanyanMonitor CI deployment runs after a push and report final status.
HomericIntelligenceRun Mojo format, markdownlint, and pre-commit hooks for code quality checks.
openkaidenInspect container images and replicate integration test failures via shell access.
