The pig CLI reference

The pig toolchain is a Python package (promptless-instruction-hub, Python 3.11 or later) that exposes two equivalent console scripts, pig and promptless-instruction-hub. Every subcommand accepts --hub to point at a hub directory other than the current one. This page documents the public subcommands.

`pig init`

Initialize an empty Instruction Hub: writes hub.yaml, the required pig package, and the asset and generated-output directories.

--org — your organization name. Defaults to Promptless.
--plugin-id — the kebab-case plugin identifier.
--plugin-name — the plugin display name.
--plugin-version — the initial version. Defaults to 0.1.0.

pig init --org "YourOrg" \
  --plugin-id your-instruction-hub \
  --plugin-name "Your Instruction Hub"

`pig scan`

Import reusable assets from a source repository and inventory its context files. pig scan imports skills from .agents/skills and MCP configs, inventories AGENTS.md, CLAUDE.md, and GEMINI.md into hub.repo-context.json, and adds references for the imported assets to the pig package.

--source — the repository to scan. Defaults to the current directory.

pig scan --source /path/to/existing/repo

`pig validate`

Validate the hub’s source files: configuration, packages, asset support modes, references, and MCP configs, and confirm there are no symlinks or literal secrets. Validation does not compile.

pig validate

`pig verify`

Run the same checks as pig validate and then fully compile the hub in a temporary directory. Your working tree is untouched, so you see a real build without generating committed output.

pig verify

`pig build`

Compile each package in stable_packages for every configured target, writing dist/<target>/<package>/ and the marketplace manifests.

--check — do not write; instead fail if the committed artifacts are stale relative to the source.

pig build
pig build --check

`pig status`

Print the local release metadata from a release manifest.

--manifest — the manifest to read. Defaults to hub.release.json.

pig status