publish

Create GitHub PRs or GitLab MRs for completed doer tickets and optionally transition Jira.

Updated May 3, 2026

Search Tags:#automation #git #workflow #publish #jira #pr #merge-request

One-click install

npx skills add https://github.com/icarloscornejo/doer --skill publish-icarloscornejo

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/icarloscornejo/doer/tree/main/skills/publish
Command: npx skills add https://github.com/icarloscornejo/doer --skill publish-icarloscornejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create PRs (GitHub) or MRs (GitLab) for a completed doer ticket, optionally transitioning the linked Jira ticket, so handoffs to code review and deployment are streamlined.

Core Features & Use Cases

Push the ticket branch to the remote and prepare it for review.
Create a PR/MR against a target base (default main) upon ticket completion.
Optionally transition the linked Jira ticket after PR/MR creation.
Support for draft PRs/MRs via the --draft flag.
Dry-run mode to preview actions without making changes.
Reuse mode to update an existing PR/MR without creating a new one.
Validate ticket completeness and repository readiness before execution.

Quick Start

Run /wk:publish <TICKET-ID> after the doer ticket completes to create a PR/MR and optionally transition Jira.

Frequently Asked Questions about publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate PR and MR creation for completed Jira tickets?▼

You can automate PR and MR creation by running the publish command on a completed ticket, which pushes the feature branch and creates a pull or merge request against the main branch while optionally transitioning the linked Jira ticket status.

Does PR and MR automation work with both GitHub and GitLab repositories?▼

PR and MR automation supports both GitHub and GitLab repositories, targeting GitHub for pull requests and GitLab for merge requests, provided the repository has a reachable remote and the appropriate CLI tools are installed.

Can I preview PR or MR creation before pushing changes to the remote?▼

You can preview PR or MR creation by using the dry-run mode, which validates ticket completeness and repository readiness and previews actions without making any actual changes to the remote repository.

How do I update an existing pull request instead of creating a new one?▼

You can update an existing pull request instead of creating a new one by using the reuse mode, which updates the existing PR or MR metadata without duplicating the review request on the remote repository.

What are the prerequisites for automating Jira ticket transitions with Git workflows?▼

Prerequisites for automating Jira ticket transitions include having a completed doer ticket, a repository with a reachable remote, and the appropriate GitHub or GitLab CLI tools installed and available before execution.

When should I use draft PRs for completed ticket branches?▼

You should use draft PRs for completed ticket branches when code is not ready for final review, utilizing the draft flag to push the feature branch and create a draft pull or merge request against the target base branch.