publish-branch

Push the current branch to origin and generate a Jira-linked PR title from commits.

7|Updated Dec 5, 2023

Search Tags:#git #jira #branch-management #pull-request #commit-history #publish-branch

Ready to run

npx skills add https://github.com/mParticle/aquarium --skill publish-branch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: publish-branch
Source: https://github.com/mParticle/aquarium/tree/main/.claude/skills/publish-branch
Command: npx skills add https://github.com/mParticle/aquarium --skill publish-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Pushes the current branch to the remote origin and automatically generates a polished PR title and description from the branch name and commit history, streamlining release workflows.

Core Features & Use Cases

Verifies a clean working state, pushes the branch, and generates a PR title and description based on commits.
Supports conventional branch naming like <type>/<description>-<TICKET> and Jira integration for traceability.
Useful for preparing PRs after feature development, enabling CI-triggered workflows, and avoiding direct pushes to main.

Quick Start

Push your current branch to origin and generate a PR title and description from your commits.

Frequently Asked Questions about publish-branch

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

FAQPage Schema

How do I auto-generate a PR description from commit history when pushing a branch?▼

You can auto-generate a PR description from commit history by pushing the current branch to the remote origin, which parses branch names and analyzes commits to produce a polished PR title and description for review.

Can I create a Jira-linked PR title from a conventional branch name?▼

Yes, you can create a Jira-linked PR title by enforcing conventional branch naming like <type>/<description>-<TICKET>, which enables Jira integration and traceability directly within the generated PR metadata.

What's the best way to prepare a feature branch for a CI-triggered workflow?▼

The best way to prepare a feature branch for a CI-triggered workflow is to verify a clean working state and push the branch to origin, automatically generating the necessary PR metadata to enable the workflow.

Does the auto-generated PR metadata require a clean working state before pushing?▼

Yes, auto-generated PR metadata requires a clean working state before pushing, as the workflow detects the repository state to safely push the current branch and analyze commits for the PR description.

Why should I use an automated branch publishing workflow instead of pushing directly to main?▼

Using an automated branch publishing workflow avoids direct pushes to main by pushing to a feature branch instead, ensuring that commit history is analyzed and a structured PR is prepared for review before integration.

How does parsing conventional branch names improve GitHub pull request creation?▼

Parsing conventional branch names improves GitHub pull request creation by extracting the ticket number and type, which structures the PR title and generates a Jira-linked description suitable for GitHub traceability.