← Back to list

phase-package
by mvillmow
Training framework written in Mojo
⭐ 11🍴 4📅 Jan 24, 2026
SKILL.md
name: phase-package description: "Create distributable packages including .mojopkg files and archives. Use during package phase to prepare components for distribution." mcp_fallback: none category: phase phase: Package user-invocable: false
Package Phase Coordination Skill
Create distributable packages including Mojo packages (.mojopkg), archives, and installation procedures.
When to Use
- Starting package phase (after Plan completes)
- Running in parallel with Test and Implementation phases
- Preparing components for distribution and reuse
- Creating installable packages or release artifacts
Quick Reference
# Build Mojo package
pixi run mojo build -o packages/module.mojopkg shared/module/
# Create distribution archive
tar -czf dist/ProjectOdyssey-v0.1.0.tar.gz packages/ examples/ README.md
# Test installation
pixi run mojo run -I packages test_import.mojo
Workflow
- Build packages - Compile Mojo modules to
.mojopkgfiles - Create archives - Package distributions (tar.gz, zip)
- Write installation docs - Document setup procedures
- Test installation - Verify in clean environment
- Create CI workflow - Automate packaging in GitHub Actions
- Generate metadata - Version info, dependencies, etc.
Package Structure
Input (module source):
shared/tensor/
├── __init__.mojo
├── ops.mojo
└── types.mojo
Output (packaged module):
packages/
├── tensor.mojopkg
├── nn.mojopkg
└── utils.mojopkg
Distribution archive:
ProjectOdyssey-v0.1.0/
├── packages/
├── examples/
├── docs/
├── README.md
├── LICENSE
└── INSTALL.md
Build Configuration
Mojo package build:
# Single module
mojo build -o packages/tensor.mojopkg shared/tensor/
# All modules (in loop or script)
for module in shared/*/; do
mojo build -o packages/$(basename $module).mojopkg "$module"
done
Archive creation:
# Tar.gz (Linux/Mac)
tar -czf dist/ProjectOdyssey-v0.1.0.tar.gz packages/ examples/ docs/
# Zip (cross-platform)
zip -r dist/ProjectOdyssey-v0.1.0.zip packages/ examples/ docs/
Quality Checklist
Before marking package complete:
- All modules compile without warnings
- Package can be imported in test script
- Examples run correctly
- README and INSTALL.md included
- LICENSE file present
- Version tagged correctly
- No compilation warnings
- Dependencies documented
Phase Dependencies
- Input from: Plan phase (deliverables and success criteria)
- Parallel with: Test phase (TDD) and Implementation phase
- Precedes: Cleanup phase (after parallel phases complete)
Output Location
- Packages:
/packages/<module>.mojopkg - Archives:
/dist/<version>.tar.gz,.zip - Documentation: GitHub issue comments
- Release artifacts: GitHub releases section (after cleanup)
Error Handling
| Error | Fix |
|---|---|
| Build fails | Check syntax, verify all files in module |
| Import fails | Verify __init__.mojo exports, check paths |
| Archive corrupted | Recreate archive, verify contents |
| Installation fails | Check permissions, test script paths |
| Missing files | Verify all deliverables before packaging |
References
CLAUDE.md- "Package Phase" in 5-phase workflow.github/workflows/- Example CI workflowspixi.toml- Build configuration and tasks
Key Principle: Package only what's been tested and approved. No untested code in releases.
Score
Total Score
60/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
✓LICENSE
ライセンスが設定されている
+10
○説明文
100文字以上の説明がある
0/10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
Reviews
💬
Reviews coming soon