bitbucket-pr-workflow

Create Bitbucket pull requests linked to Jira from active task metadata.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/hjemmesidekongen/ai --skill bitbucket-pr-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bitbucket-pr-workflow
Source: https://github.com/hjemmesidekongen/ai/tree/main/plugins/herold/skills/bitbucket-pr-workflow
Command: npx skills add https://github.com/hjemmesidekongen/ai --skill bitbucket-pr-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of Bitbucket Pull Requests directly from your active task, ensuring consistency and saving valuable development time.

Core Features & Use Cases

  • Automated PR Creation: Generates PRs with structured descriptions based on task details.
  • Jira Integration: Links the created PR back to the Jira ticket with a comment and optionally transitions the ticket status.
  • Pipeline Status Check: Monitors the CI pipeline status after PR creation and reports the outcome.
  • Use Case: After completing a feature development task, you can invoke this Skill to automatically create a PR, populate its description with the task's summary and acceptance criteria, assign reviewers, and link it back to Jira.

Quick Start

Use the bitbucket pr workflow skill to create a pull request for the active task.

Frequently Asked Questions about bitbucket-pr-workflow

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

FAQPage Schema
How do I automate Bitbucket pull request creation from Jira tasks?

Automating Bitbucket pull request creation from Jira tasks involves generating PRs with structured descriptions populated from task keys, summaries, and acceptance criteria, then linking the PR back to Jira. This workflow ensures consistency and saves development time by orchestrating PR generation directly from active tasks.

Can I link a Bitbucket pull request to Jira and transition the ticket status automatically?

Linking a Bitbucket pull request to Jira automatically adds a comment to the Jira ticket and optionally transitions its status. This integration connects the created PR directly back to the corresponding Jira issue, ensuring development tracking remains synchronized across both platforms.

Does Bitbucket PR workflow check CI/CD pipeline status after creating a pull request?

Bitbucket PR workflow checks CI/CD pipeline status immediately after pull request creation and reports the outcome. Monitoring the pipeline post-creation ensures you receive immediate feedback on whether the continuous integration checks passed for the newly generated PR.

What happens if Bitbucket or Jira MCP services are unavailable during PR creation?

If Bitbucket or Jira MCP services are unavailable during PR creation, the workflow employs graceful fallback mechanisms to handle the missing services. These fallbacks prevent total failure, allowing the process to degrade safely when external integrations are temporarily inaccessible.

How do I populate a Bitbucket PR description using Jira acceptance criteria?

Populating a Bitbucket PR description using Jira acceptance criteria extracts the task summary and acceptance criteria from the active Jira task to automatically generate a structured description. This ensures the PR documentation accurately reflects the defined requirements without manual copy-pasting.

Do I need Bitbucket and Jira MCP services configured to automate developer workflows?

You need Bitbucket and Jira MCP services configured to fully automate developer workflows, although graceful fallback mechanisms exist for unavailable services. Having both services active ensures complete PR creation, Jira linking, and pipeline status monitoring without degraded functionality.