| name | generate-pack |
| description | Regenerate harness-native pack output and marketplaces from portable source. Use after source edits, before dogfooding, release preparation, or drift checks. |
Generate Pack
Purpose
Use this skill to run packport generation primitives in the right order without hand-editing generated output.
Workflow
- Identify the pack repository root and target set: Claude Code, OpenCode, Codex, or all.
- Run
packport check <root> before generation. Stop on errors.
- For Claude Code user packs, run
packport claude generate <root>.
- For OpenCode user packs, run
packport opencode generate <root> <root>/.packs/opencode.
- For Codex user packs, run
packport codex generate <root>.
- In the packport repository only, include control packs for dogfood output with
--include-control-packs on OpenCode and Codex generation.
- In the packport repository only, refresh Claude control plugins with
packport control-plugin claude .packs/claude/packport, packport control-plugin claude configport .packs/claude/configport, and packport control-plugin claude-marketplace ..
- If working from the packport source tree before a binary is installed, use
bun src/cli.ts in place of packport.
- Run
packport check <root> again and report changed generated paths and diagnostics.
Boundaries
- Do not use
--include-control-packs in ordinary pack repositories unless the user explicitly asks for tool-owned control output.
- Do not edit generated files to fix generation results; edit source packs or configport state and regenerate.
- Do not materialize profile-local answers into committed
.packs/ output.
