Skip to main content

v2.63.0

Released 2026-09-28. The CLI half of the Orunbase skill work (orun-cloud epic saas-agent-skills): the practices a workspace expects an agent to follow are hosted skills, copied at setup, kept honest by revision, and — when a repository asks — enforced.

Binaries and the merged-pull-request list are on the GitHub releases page.

orun skills pull writes the whole bundle, where your client looks​

A skill revision can carry files now: references/* an agent loads on demand and templates/* it copies. pull writes them beside SKILL.md, and removes a file an earlier pull wrote that the new revision no longer has — recorded in .orun-files, so anything you put in the directory yourself is never touched.

--client resolves the directory a coding-agent client discovers skills in, so the setup prompt can say one thing for every client:

orun skills pull --client claude-code      # ~/.claude/skills
orun skills pull --client codex            # ~/.codex/skills
orun skills pull --client cursor           # ~/.cursor/skills
orun skills pull --client vscode --project # .github/skills of this repository

--dir still names a directory outright and wins.

orun skills status​

The skills on disk against the registry: current, stale (pull again), unknown (edited, or from elsewhere), missing. Exit 1 when anything is not current, so a session-start hook can call it and pull only when needed.

See orun skills.

orun pr check --standards off|warn|enforce​

The provenance rules under a mode, plus four that need the checkout: skill-current, task-contract, affects-ceiling, epic-status. warn (the default) never fails what passes today; enforce turns the missing manifest and missing skill pins into errors and fails an unknown pin, a missing or unattached contract, and a diff outside the contract's affects. Resolved from --standards, then ORUN_STANDARDS, then a new execution.standards in intent.yaml. In a GitHub Actions pull_request job the manifest is read from the event's PR body, so one CI line is the whole gate. The cloud's orun/compliance check replays the same conformance fixture under the same modes.

Removed in v2.67.0.