bitbucket-pipeline

Manage Bitbucket Pipelines via the Bitbucket REST API.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/tanyagray/claude --skill bitbucket-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bitbucket-pipeline
Source: https://github.com/tanyagray/claude/tree/main/plugins/bitbucket/skills/bitbucket-pipeline
Command: npx skills add https://github.com/tanyagray/claude --skill bitbucket-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bitbucket Pipelines management is manual and error-prone; this skill provides programmatic control to monitor, trigger, and configure pipelines via REST API.

Core Features & Use Cases

  • List pipelines, get details, trigger runs, stop runs, and manage pipeline variables and configurations across Bitbucket Cloud workspaces.
  • Use Case: A DevOps engineer wants to auto-rollback on failures by triggering a new run and inspecting logs.
  • Use Case: Automate validation of pipeline configurations before merging code.

Quick Start

Trigger a pipeline for the current repository via the REST API.

Frequently Asked Questions about bitbucket-pipeline

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

FAQPage Schema
How do I trigger Bitbucket Pipelines automatically through the REST API?

You can trigger Bitbucket Pipelines automatically by calling the Bitbucket REST API endpoints provided by this Skill, which requires API access tokens and environment variables to authenticate and start the pipeline run.

Can I check pipeline status and view logs across Bitbucket Cloud workspaces?

Yes, you can check pipeline status and view logs across Bitbucket Cloud workspaces by using the Skill's REST endpoints to list pipelines and retrieve detailed execution logs for monitoring ongoing or completed runs.

Do I need API access tokens to manage Bitbucket Pipelines programmatically?

Yes, managing Bitbucket Pipelines programmatically requires API access tokens and environment variables to authenticate REST API requests for listing, triggering, stopping, and configuring pipelines across your repositories.

What's the best way to automate validation of pipeline configurations before merging code?

The best way to validate pipeline configurations before merging code is using this Skill to programmatically inspect and manage pipeline variables and configurations via the Bitbucket REST API, ensuring setup correctness before integration.

How do I stop a running Bitbucket Pipeline via REST API?

You can stop a running Bitbucket Pipeline by sending a request through the Skill's dedicated REST API endpoints, which interface directly with Bitbucket Cloud to halt active pipeline executions programmatically.