# Publish

> Publish completed work on a typed branch and optionally open a GitHub PR. Uses an approved draft with concrete QA steps and a high-level Mermaid Change diagram (Before/After for rework). Any agent that opens a PR follows the same ship contract, not only this skill. Use after work is complete when the user wants to ship a branch or PR. Never use inside /task.

- Skill: `beskars-code/publish` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add beskars-code/publish`
- Raw SKILL.md: https://api.skillmd.com/api/skills/beskars-code/publish/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: beskars-code (https://skillmd.com/u/beskars-code)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/beskars-code/publish

---


# Publish

**Must read:** [../pack-shared/standards.md](../pack-shared/standards.md) — Read `/taste` and `/architecture` doctrines this turn so the Change diagram and QA match the shipped structure. Do not skip. Every PR this pack opens also follows [../pack-shared/pr-ship.md](../pack-shared/pr-ship.md) (create tool) — including `/just-do-it` and cloud agents, not only this skill.

**Read:** [doctrine.md](doctrine.md) · [reference.md](reference.md) · [../pack-shared/pr-ship.md](../pack-shared/pr-ship.md) · **Ask style:** [../pack-shared/asking.md](../pack-shared/asking.md)

This skill is a user start. Do not nest it under `/task`. Publish only. Never invent a `publish-flow` name, write tracker issues, or implement product work.

## Process

1. Inspect git and stop on unsafe states. Before a commit, run this repo’s
   `lint` and `test` (`test:quality` when that is the test script).
2. Lock change type and ticket.
3. Create or reuse the typed branch, then push unless local-only.
4. Ask whether to draft and publish a PR.
5. Show the full title and body (including the Mermaid Change diagram).
6. Create the PR only after approval, using the create tool in
   [pr-ship.md](../pack-shared/pr-ship.md).

Templates, branch rules, question batches, and failure handling live in the reference and doctrine.