mcpField
P
publish

publish

github.com/gabriel-lafranceDevelopment055 installsUpdated 1d ago
Repository

About publish

A publishing workflow skill for preparing and opening pull requests without implementing product changes or creating tracker issues. It guides branch handling, CI checks, approval, and PR creation using the repository’s shipping rules.

Key features

  1. 01Git state and safety checks
  2. 02Change type and ticket selection
  3. 03Typed branch reuse or creation
  4. 04CI mirror before relevant pushes
  5. 05Approval before PR publication
  6. 06PR title and body preview

Use cases

  1. 01Preparing a branch for publication
  2. 02Checking changes before a push
  3. 03Drafting a PR for approval
  4. 04Opening a PR under repository rules

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gabriel-lafrance/skills --skill publish

After installing, type/publishin Claude Code to confirm it loaded.

Bundled filesdoctrine.mdreference.md

Details

From the project README

Publish

Must read: ../pack-shared/standards.md. Apply the Taste and Architecture sections of AGENTS.md 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 (create tool), including /just-do-it and any agent that ships a branch, not only this skill.

Read: doctrine.md · reference.md · ../pack-shared/pr-ship.md · Ask style: ../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 push that opens a PR, or a commit or push on a branch that already has an open PR, run the CI mirror in pr-ship.md in this environment. Do not run it on a commit you are not pushing.
  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.

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

Comments

Markdown supported