bitbucket-jira-cli
Manage Bitbucket and Jira from the Terminal
Bitbucket and Jira workflows often require separate tools and repeated context switching. This skill maps both services into focused bj CLI operations.
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "bitbucket-jira-cli" from https://skillstore.io/skills/spenhouet-bitbucket-jira-cli.md and its manifest at https://skillstore.io/api/skills/spenhouet-bitbucket-jira-cli/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "bitbucket-jira-cli". Show my open pull requests and identify items that need attention.
Expected outcome:
- Three open pull requests were found.
- Pull request 128 needs one reviewer and has a successful pipeline.
- Pull request 131 has a failed test pipeline and should be investigated first.
Using "bitbucket-jira-cli". Preview a pull request for feature/PROJ-42-validation without changing anything.
Expected outcome:
Preview: create a pull request titled from PROJ-42, link the Jira issue, and transition it to In Progress. No changes were made.
Using "bitbucket-jira-cli". Summarize the latest pipeline for the main branch.
Expected outcome:
The latest main pipeline failed during integration tests. The build and lint stages passed, and no retry was started.
Security Audit
CriticalMost backtick and device-file alerts are false positives caused by Markdown syntax and harmless output redirection. Unix and Windows instructions execute downloaded installers directly. The skill also directs agents to install a dependency without explicit approval.
Confirmed security concerns (2)
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (50)
🌐 Network access (1)
📁 Filesystem access (7)
Detected Patterns
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/spenhouet-bitbucket-jira-cli/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/spenhouet-bitbucket-jira-cli?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/spenhouet-bitbucket-jira-cli?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/spenhouet-bitbucket-jira-cli/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/spenhouet-bitbucket-jira-cli.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
spenhouet. (2026). bitbucket-jira-cli security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/spenhouet-bitbucket-jira-cli/audits/2BibTeX citation
@techreport{spenhouet-spenhouet-bitbucket-jira-cli-2026,
author = {spenhouet},
title = {bitbucket-jira-cli security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/spenhouet-bitbucket-jira-cli/audits/2},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "bitbucket-jira-cli security audit report (audit version 2)"
version: "unspecified"
type: report
authors:
- name: "spenhouet"
date-released: "2026-07-13"
url: "https://skillstore.io/skills/spenhouet-bitbucket-jira-cli/audits/2"
identifiers:
- type: other
value: "skillstore:spenhouet-bitbucket-jira-cli:audit:2"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Coordinate Feature Delivery
Create and review Bitbucket pull requests while linking work to Jira issues from a feature branch.
Manage Release Pipelines
Inspect pipelines, run branch builds, and coordinate Jira status changes during release preparation.
Review Team Progress
List open pull requests and assigned Jira issues to review delivery status.
Try These Prompts
Check whether bj is installed and show my Bitbucket and Jira authentication status. Do not install or authenticate without my approval.
List my open Jira issues and open Bitbucket pull requests. Summarize priorities, reviewers, and pipeline status without changing remote state.
Prepare a pull request for branch {branch}. Use Jira key {issue_key}, preview all effects, and ask before creating anything.Review pull request {pr_id}, its diff, pipeline results, and Jira issue {issue_key}. Propose actions and request confirmation before any remote change.Best Practices
- Use dry-run before creating or merging a pull request when Jira branch automation is active.
- Confirm the workspace, repository, Jira issue, and requested state change before using non-interactive approval.
- Request only necessary token scopes and avoid exposing raw API output containing sensitive fields.
Avoid
- Do not run remote installer scripts or install packages without explicit user approval.
- Do not pass automatic confirmation flags for merges, closures, pipeline stops, or Jira transitions without verified intent.
- Do not print, store, or include Bitbucket and Jira tokens in prompts or outputs.