bitbucket
/bitbucket
Wspiera pracę z Atlassian Bitbucket: Bitbucket Pipelines, pull requesty, uprawnienia gałęzi i integracja z Jira, przy zarządzaniu repozytoriami i CI/CD w Bitbucket Cloud i Server.
- Autor
- G1Joshi ↗
- Repozytorium
- Agent-Skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 01.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 01.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wspiera pracę z Atlassian Bitbucket: Bitbucket Pipelines, pull requesty, uprawnienia gałęzi i integracja z Jira, przy zarządzaniu repozytoriami i CI/CD w Bitbucket Cloud i Server.
Oryginalny opis (EN)
Expert Atlassian Bitbucket assistance covering Bitbucket Pipelines, pull requests, branch permissions, and Jira integration. Use when managing repositories and CI/CD workflows on Bitbucket Cloud/Server.
Jak działa
- When to Use
- Quick Start
- Core Concepts
- Common Patterns
- Best Practices
- Troubleshooting
- References
Podgląd SKILL.md
---
name: bitbucket
description: Expert Atlassian Bitbucket assistance covering Bitbucket Pipelines, pull requests, branch permissions, and Jira integration. Use when managing repositories and CI/CD workflows on Bitbucket Cloud/Server.
---
# Bitbucket
Bitbucket is Atlassian's Git solution. Its superpower is **Jira Integration**.
## When to Use
- **Enterprise Git Hosting with Atlassian Ecosystem**: Tightly integrated Git repositories with Jira Software and Confluence.
- **Bitbucket Pipelines (CI/CD)**: Cloud-native CI/CD defined in `bitbucket-pipelines.yml` without external build servers.
- **Branch Permissions & Merge Checks**: Enforcing minimum approvals, successful builds, and resolved tasks before merging.
- **Bitbucket Cloud REST API v2**: Automating repository provisioning, PR management, and user permissions.
## Quick Start
```yaml
# bitbucket-pipelines.yml
image: node:20
pipelines:
default:
- step:
name: Build and Test
caches:
- node
script:
- npm ci
- npm test
```
## Core Concepts
### Declarative CI/CD Pipeline (bitbucket-pipelines.yml)
Automating test, build, and deployment pipelines:
```yaml
# bitbucket-pipelines.yml
image: node:22-alpine
pipelines:
default:
- step:
name: Lint and Unit Tests
caches:
- node
script:
- npm ci
- npm run lint
- npm test -- --coverage
branches:
main:
- step:
name: Build and Push Container
services:
- docker
caches:
- docker
script:
- export IMAGE_TAG=$BITBUCKET_COMMIT
- docker build -t myregistry.com/app:$IMAGE_TAG .
- echo "$REGISTRY_PASSWORD" | docker login -u "$REGISTRY_USER" --password-stdin myregistry.com
- docker push myregistry.com/app:$IMAGE_TAG
- step:
name: Deploy to Production
deployment: production
trigger: manual # Requires manual approval in UI
script:
- echo "Deploying version $BITBUCKET_COMMIT to production..."
```
### Bitbucket REST API v2 Operations with Curl
Querying pull requests and triggering builds programmatically:
```bash
# Fetch open pull requests using personal access token
curl -s -X GET \
-H "Authorization: Bearer $BITBUCKET_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
"https://api.bitbucket.org/2.0/repositories/my-workspace/my-repo/pullrequests?state=OPEN" | jq .
```
### Jira Smart Commits Integration
Transitioning Jira issues and logging time via Git commit messages:
```bash
# Commit message format: <Issue-Key> #<command> [optional comments]
git commit -m "PROJ-1029 #resolve Added rate limiting to billing endpoint"
git commit -m "PROJ-1029 #time 2h 30m #comment Refactored token validation"
```
## Common Patterns
### Deployment Environments with Manual Approval Gates
**Problem**: Continuous delivery deploying to production before QA review.
**Solution**:
Use Bitbucket environment triggers with manual gates:
```yaml
pipelines:
branches:
main:
- step:
name: Test & Build
script:
- npm test
- step:
name: Deploy to Staging
deployment: staging
script:
- ./deploy-staging.sh
- step:
name: Deploy to Production
trigger: manual
deployment: production
script:
- ./deploy-prod.sh
```
## Best Practices
**Do**:
- Configure Merge Checks to require successful pipeline builds and minimum reviewer approvals on protected branches.
- Use Repository Variables (masked and secured) for cloud API credentials and deployment tokens.
- Use `deployment: production` steps to track deployment history and rollback status in Jira.
- Leverage Bitbucket Pipeline caches (`caches: - node`, `- docker`) to accelerate build execution.
**Don't**:
- Allow force-pushing (`git push --force`) to `main` or release branches.
- Store plaintext passwords or tokens in `bitbucket-pipelines.yml`.
- Run long deployment steps without explicit `trigger: manual` on production environments.
## Troubleshooting
| Error | Cause | Solution |
| :------------------------------------------------------- | :---------------------------------------------------------------- | :------------------------------------------------------------------ |
| `Configuration error in bitbucket-pipelines.yml` | Invalid YAML indentation or unsupported pipeline keyword. | Validate syntax using Bitbucket Pipelines Validator tool. |
| `Pipeline build step timed out after 120 minutes` | Long-running test or hanging process exceeded timeout. | Add `max-time: 30` to step configuration and inspect logs. |
| `Permission denied (publickey) on git clone in pipeline` | SSH key not added to Bitbucket Repository Settings > Access Keys. | Generate SSH key pair in Pipeline Settings and register public key. |
## References
- [Bitbucket Documentation](https://support.atlassian.com/bitbucket-cloud/)
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · G1Joshi/Agent-Skills | 100 | MIT |
| TerminalSkills/skills | 100 | Apache-2.0 |
| Apra-Labs/agent-marketplace | 100 | Apache-2.0 |
| OpenHands/extensions | 100 | MIT |
| HelixDevelopment/agent | 92 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki db9d41586542 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90bkt
Obsługuje repozytoria, pull requesty, gałęzie, pipeliny i uprawnienia w Bitbucket Cloud lub Data Center przez CLI bkt. - 90atlassian-admin
Administruje produktami Atlassian (Jira, Confluence, Bitbucket, Trello): użytkownicy, grupy, uprawnienia, SSO, aplikacje marketplace, polityki bezpieczeństwa i ustawienia organizacji. - 90atlassian-admin
Administruje produktami Atlassian (Jira, Confluence, Bitbucket, Trello): użytkownicy, grupy, uprawnienia, SSO, aplikacje marketplace, polityki bezpieczeństwa i ustawienia organizacji. - 87lantern-bitbucket
Przegląda, otwiera i komentuje pull requesty w Bitbucket Cloud z terminala, korzystając z konta dodanego w Lanternie. - 100jira-issue-to-pr
Konfiguruje automatyzację odpytującą Jira o zgłoszenia create-pr i tworzącą pull requesty w GitHubie, merge requesty w GitLabie lub pull requesty w Bitbucket. - 90diagnose-ci
Diagnozuje nieudany przebieg CI w GitLab, GitHub Actions, Azure Pipelines lub Bitbucket i wskazuje przyczynę awarii.