skills.rest
shoshoavi
shoshoaviCOMMUNITY
Explore all skills by this author →
GitHub

jira-branch-git-workflow

Automates git commit, push, and PR creation using Jira tickets parsed from feature branch names.

Updated Apr 15, 2026
Search Tags:#git#workflow#pull request#jira#github cli#commit automation#branch parsing
One-click install
npx skills add https://github.com/shoshoavi/agentic_worflows --skill jira-branch-git-workflow-shoshoavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-branch-git-workflow
Source: https://github.com/shoshoavi/agentic_worflows/tree/main/cursor/skills/jira-branch-git-workflow
Command: npx skills add https://github.com/shoshoavi/agentic_worflows --skill jira-branch-git-workflow-shoshoavi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually writing consistent commit messages, pushing feature branches, and creating pull requests tied to Jira tickets is repetitive and error-prone, especially when remote commit-message regex rules reject malformed messages. ## Core Features & Use Cases - Automatic Branch Parsing: Extracts the Jira ticket (e.g., PE-1111) and feature name from branches matching the feature/PE-NUMBER-Name convention without asking the user. - Standardized Commits and PRs: Generates commit messages in the {TICKET} - {Description} format, pushes the full branch, and creates or finds the matching GitHub PR via the gh CLI, always sharing the PR link. - Use Case: You finish a fix on feature/PE-2345-FixAuthBug and ask to commit and push. The Skill stages your files, commits as PE-2345 - FixAuthBug, pushes the branch, creates a PR with a Jira link, and returns the PR URL. ## Quick Start Commit my staged changes, push this branch, and create a PR for it.

Frequently Asked Questions about jira-branch-git-workflow

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

FAQPage Schema
How do I auto-generate commit messages from a Jira branch name?▼

Parse the branch with git branch --show-current and sed to extract the ticket (e.g., PE-1111) and name, then commit using the format "{TICKET} - {Description}". The description must start with a capital letter to pass remote regex validation.

How to create a GitHub PR from the command line with gh?▼

Use gh pr create with a title and body after pushing the branch. First check for an existing PR with gh pr list --head to avoid duplicates, and always output the PR URL afterward.

What branch naming convention does this workflow require?▼

Branches must follow the pattern feature/PE-NUMBER-Name, such as feature/PE-1111-SundayFundayBot. If the branch does not match, the workflow falls back to asking the user for a manual commit message.

Why is my git push rejected due to commit message format?▼

The remote enforces a regex requiring messages like "PE-1111 - Description" with a capitalized description. Rejection can come from any unpushed commit, not just the latest, so fix older bad commits with interactive rebase before retrying.

Can I use conventional commit prefixes like feat: or fix: with this workflow?▼

No. The ticket number itself is the required prefix, so messages must start with "{TICKET} - " and must not include prefixes like feat: or fix:.

Related Skills

Explore More Software Engineering Skills→
shysssthanhtrishysssthanhtri

conventional-commit

Generate Conventional Commit messages from staged Git diffs with Jira ticket IDs.

Community
Intermediate
awfixers-stuffawfixers-stuff

impl-review

Check out a pull request branch, apply reviewer feedback, and push changes.

Official
Advanced
marin-communitymarin-community
3.2k

commit

Automates linting, committing, PR creation, and monitoring for GitHub branches.

Official
Advanced
AdelysAlbertoAdelysAlberto
1

commit

Generates Conventional Commits messages with ticket IDs extracted from git branch names.

Community
Intermediate