bitbucket-pr-resolver

Fetches Bitbucket PR review comments, triages findings, and applies fixes with documented replies.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jhannka/php-skills --skill bitbucket-pr-resolver-jhannka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bitbucket-pr-resolver
Source: https://github.com/jhannka/php-skills/tree/main/skills/bitbucket-pr-resolver
Command: npx skills add https://github.com/jhannka/php-skills --skill bitbucket-pr-resolver-jhannka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a Bitbucket pull request often leaves you with dozens of scattered comments from human reviewers or automated audit tools, and it is easy to lose track of which findings are real bugs, which are false positives, and whether fixes were actually pushed before comments were resolved. ## Core Features & Use Cases - Comment Fetching and Triage: Pulls active PR comments via PowerShell scripts and classifies each as a real bug, false positive, or tech debt with a documented diagnosis. - Structured Resolution Plan: Generates a markdown checklist mapping every comment ID to the affected file and planned action, requiring explicit user approval before any code change. - Reply, Resolve, and Remember: Replies to false positives with technical justification, resolves fixed comments only after pushing, and saves decisions to persistent memory plus the project skill registry. - Use Case: A reviewer leaves 15 comments on your Laravel backend PR; the skill fetches them, verifies each against the current code, fixes the genuine bugs, justifies the false positives, and records the lessons learned. ## Quick Start Resolve the review comments on Bitbucket PR number 42 by fetching them, triaging each finding, and proposing a fix plan for my approval.

Frequently Asked Questions about bitbucket-pr-resolver

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

FAQPage Schema
How do I resolve Bitbucket PR review comments automatically?

Fetch the active comments with the get_pr_comments.ps1 script, triage each as a real bug, false positive, or tech debt, then present a plan for approval. Fix real bugs, reply to false positives with justification, and resolve comments only after pushing the fix.

How do I reply to a Bitbucket PR comment from the command line?

Use the post_pr_reply.ps1 script with the PR ID, comment ID, and a message containing your technical justification. Avoid backticks inside the message when calling it through a Bash tool, since they trigger shell command substitution and corrupt the reply text.

Why do resolved PR comments reappear in the next review pass?

Automated reviewers re-scan the pushed diff, not local commits. If you resolve a comment before pushing the fix to the remote branch, the reviewer sees the old code and raises duplicate findings, so always push first and resolve after.

Can I trust a PR review comment's description of the code?

Not always. Comments may reference code that was already fixed by later commits or a stale diff, so always read the current file before acting on a comment's text. The comment alone is not reliable evidence of the file's present state.

What are the limitations of this PR resolution workflow?

It depends on local PowerShell scripts with hardcoded Windows paths and a correct Bitbucket repo slug, which must be confirmed via git remote -v. It also requires Engram memory tooling and explicit user approval, so it is not a fully unattended automation.