Skip to content
pubm

Coding Agent Integration

This guide is for teams that already use coding agents such as Claude Code or Codex and want to add pubm release workflows to that setup.

Quick install with pubm setup-skills

Section titled “Quick install with pubm setup-skills”

The fastest way to install coding agent skills is:

Terminal window
pubm setup-skills

This downloads the skill bundle for your agent, whether that is Claude Code, Codex CLI, or Gemini CLI, from the pubm GitHub repository and places it in the correct directory. It is also available as the last step of pubm init.

Start with setup automation

Section titled “Start with setup automation”

If a repository is not wired yet, the most important agent action is setup, not publish.

Use publish-setup first. That skill handles:

  • installing the pubm plugin bundle
  • generating or updating pubm config
  • wiring CI
  • enabling changesets
  • optionally wiring version-sync targets

Give the agent the INSTALLATION.md link so it can fetch the bundle and follow the checked-in setup flow.

What the pubm plugin gives your agent

Section titled “What the pubm plugin gives your agent”

The repository ships an agent-facing bundle under plugins/pubm-plugin/.

The bundle currently contains:

  • a Claude Code plugin manifest at plugins/pubm-plugin/.claude-plugin/plugin.json
  • a checked-in skill bundle under plugins/pubm-plugin/skills/

Included skills

Section titled “Included skills”

publish-setup

Section titled “publish-setup”

Use this first when wiring pubm into a repository through an agent.

publish-preview

Section titled “publish-preview”

Use this when the agent should explain the release plan before it changes git state or publishes anything.

publish

Section titled “publish”

This is the guarded publish path. It is preview-first and requires confirmation before the real publish command.

version-sync

Section titled “version-sync”

Use this to find and wire version references outside package manifests such as docs snippets, metadata files, and sidecar config.

create-plugin

Section titled “create-plugin”

Use this when the agent needs to scaffold a new pubm plugin package with hooks, commands, and tests.

Claude Code installation

Section titled “Claude Code installation”

Claude Code uses a marketplace-based plugin model.

Typical flow:

  1. add the marketplace
  2. install the plugin from that marketplace
  3. choose the installation scope in Claude Code
/plugin marketplace add your-org/claude-plugins
/plugin install plugin-name@marketplace-name

If you are not using a marketplace, give the agent the INSTALLATION.md link instead.

Integration model

Section titled “Integration model”
  • keep runtime release behavior in pubm itself or in a pubm plugin
  • keep agent workflow and approval policy in checked-in skills
  • keep setup automation authoritative for repository onboarding

Skills and command surface

Section titled “Skills and command surface”

Skills should orchestrate the CLI, not replace it.

  • use pubm commands for deterministic release operations
  • use skills for setup sequencing, project inspection, safety checks, and approvals

Safety rules to encode

Section titled “Safety rules to encode”
  • setup before publish in new repositories
  • preview before publish in existing repositories
  • explicit approval before irreversible actions
  • plain-language summaries of versions, registries, and side effects
  • stop when git state, auth, or CI assumptions are not ready

Practical advice

Section titled “Practical advice”
  • treat publish-setup as the primary integration surface
  • keep setup automation and publish automation in the same checked-in bundle
  • expose pubm commands directly rather than translating them into vague natural-language actions
  • treat pubm as the last step, not the default step