feat: add raise-pr and bug-fix skills with Jira integration (v0.7.0)

[its-mitesh-kumar]

Summary

• Adds raise-pr skill that automates the full PR workflow (detect workspace, build, generate changeset, commit, push, create PR) for both rhdh-plugins and community-plugins monorepos
• Auto-detects which repo you're in via git remote -v and adapts PR template, npm scope, and upstream target accordingly
• Supports --a auto-approve mode to skip all approval gates for unattended workflows
• Built-in Jira integration — accepts a Jira key or URL, includes it in branch name and commit trailer, and performs post-PR Jira comment
• Adds bug-fix skill for end-to-end bug fixing from Jira tickets with Playwright-based before/after screen recordings
• Automated GIF embedding — uploads before/after GIFs to the feature branch via GitHub Contents API and embeds raw.githubusercontent.com URLs directly in the PR description
• Screenshot + DOM diagnosis — captures screenshots, DOM snapshots, and computed styles during reproduction for deeper root-cause analysis
• Auto-generated Test Plan — PR descriptions include a reviewer-facing verification checklist derived from Jira steps-to-reproduce
• Reviewer disclaimer — bug-fix PRs include a note asking reviewers to verify thoroughly before merging
• Bumps version to v0.7.0

Architecture

Context

Extracts and generalizes the existing Cursor command (rhdh-plugins/.cursor/commands/pr.md) and its #3679 enhancement into a portable agent skill that works across both plugin monorepos.

The raise-pr skill has first-class Jira support — any PR linked to a Jira issue gets automatic branch naming (fix/<workspace>-<JIRA-KEY>-<slug>), a Fixes: commit trailer, a ## Fixed section in the PR body, and a post-PR Jira comment via MCP.

The bug-fix skill chains into raise-pr after reproducing and fixing a bug: it writes a Playwright reproduction test with video recording, captures diagnostic context (screenshot + DOM + computed styles) to pinpoint the root cause, applies the fix, captures before/after recordings, converts them to GIFs, generates a test plan for reviewers, and creates the PR with embedded visual evidence.

How to Use

Prerequisites

• gh CLI — GitHub CLI must be installed and authenticated (gh auth status should show logged in). Install: https://cli.github.com/
• Jira MCP — The Atlassian Rovo MCP server must be configured in Cursor for Jira comment updates. Setup guide: https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/
  • If not configured, the skill will skip Jira updates and log a warning.
• Working checkout of rhdh-plugins (or community-plugins)
• yarn available on PATH
• ffmpeg on PATH (for converting screen recordings to GIFs). Install if missing: which ffmpeg || brew install ffmpeg

Install

Install from local checkout (while PR is unmerged):

cd /path/to/rhdh-plugins
npx skills add /path/to/rhdh-skill --skill bug-fix
npx skills add /path/to/rhdh-skill --skill raise-pr

After merge:

npx skills add redhat-developer/rhdh-skill --skill bug-fix
npx skills add redhat-developer/rhdh-skill --skill raise-pr

Invoke

/bug-fix RHDHBUGS-1234
/bug-fix https://redhat.atlassian.net/browse/RHDHBUGS-1234

What it does

1. Fetches the Jira issue (summary, description, steps to reproduce, component)
2. Maps the Jira component to a workspace (e.g., "Lightspeed" → workspaces/lightspeed)
3. Discovers e2e infrastructure (Playwright config, helpers, translations)
4. Writes a temporary reproduction test with video recording enabled
5. Runs the test — expects it to fail (bug reproduced), captures "before" video
6. Captures diagnostic context — takes a screenshot, DOM snapshot, and computed styles of the target element for precise root-cause analysis
7. Diagnoses root cause (cross-referencing captured DOM/styles with source code) and applies the fix
8. Re-runs the test — expects it to pass (fix verified), captures "after" video
9. Converts .webm recordings to GIFs via ffmpeg
10. Generates a Test Plan — builds a markdown checklist from Jira steps-to-reproduce + fix verification + regression checks
11. Deletes the reproduction test (not included in the PR)
12. Chains into raise-pr — builds, generates changeset, commits, pushes, uploads GIFs to branch via GitHub Contents API, creates PR with before/after GIFs embedded + Test Plan + reviewer Note, then adds a comment on the Jira issue

Using raise-pr standalone with Jira

raise-pr RHDHBUGS-1234
raise-pr https://redhat.atlassian.net/browse/RHIDP-15252

When a Jira key is provided, raise-pr automatically:

• Names the branch as fix/<workspace>-<JIRA-KEY>-<slug>
• Adds a Fixes: trailer in the commit message
• Includes a ## Fixed section in the PR body with the Jira link
• After PR creation: adds a comment on the Jira issue via MCP

PR Body Sections (conditional)

The generated PR description includes these sections based on context:

Section	Included when...
## Description	Always
## Fixed	jira_key is provided
## UI before changes / ## UI after changes	recordings are provided (GIFs uploaded to branch)
## Test Plan	test_plan is provided by caller
## Checklist	Always
## Note	Both recordings AND jira_key are present (automated bug-fix PR)

Key Design Decisions

• GIF upload happens BEFORE gh pr create — GIFs are uploaded to the fork branch via GitHub Contents API, and the resulting raw.githubusercontent.com URLs are embedded directly in the PR body. No gh pr edit or manual drag-and-drop needed.
• Simplified Jira integration — Only add_jira_comment MCP call (with correct body param) is used post-PR. Web Link and Transition steps were removed because the corresponding MCP tools don't exist and acli is a paid third-party tool.
• Screenshot + DOM capture in diagnosis — The agent captures runtime state (screenshot, outerHTML, computed styles) before any fix is applied, providing concrete evidence for root-cause identification rather than guessing from source alone.
• Auto-generated Test Plan — Derived from Jira steps-to-reproduce (inverted into verification steps) + expected behavior after fix + regression checks.
• Reviewer disclaimer — Bug-fix PRs include a ## Note section reminding reviewers this was agent-generated and should be verified thoroughly.

Files

raise-pr skill

• New: skills/raise-pr/SKILL.md — 11-step workflow with repo auto-detection, --a auto-approve mode, Jira context resolution, GIF upload via Contents API, and post-PR Jira comment
• New: skills/raise-pr/references/repo-profiles.md — per-repo config (upstream remote, npm scope, PR body template with conditional Jira/recording/test-plan/note sections)
• New: skills/raise-pr/references/jira-input.md — shared Jira key/URL parsing logic and REST API patterns

bug-fix skill

• New: skills/bug-fix/SKILL.md — 8-step workflow (fetch Jira issue, identify workspace, reproduce with video, diagnose with screenshot+DOM capture, fix, verify, convert videos, generate test plan, chain into raise-pr)
• New: skills/bug-fix/references/workspace-map.md — Jira component to rhdh-plugins workspace directory mapping with runtime discovery instructions
• New: skills/bug-fix/references/e2e-patterns.md — shared Playwright patterns across all workspaces (multi-locale, dual-mode, translation helpers, MUI patterns, repro test template)
• New: skills/bug-fix/references/video-recording.md — Playwright video config, ffmpeg conversion, and automated GitHub Contents API embedding workflow

Metadata

• Modified: README.md — added Bug Fix section, updated raise-pr description with Jira integration mention
• Modified: pyproject.toml, .claude-plugin/plugin.json, .claude-plugin/marketplace.json — version bump to 0.7.0

Test plan

• uv run pytest passes (321 passed, 1 pre-existing failure unrelated to this PR)
• Skill structure tests pass (test_skill_structure.py)
• Marketplace/version tests pass (test_marketplace.py)
• Install via npx skills add redhat-developer/rhdh-skill --skill raise-pr and verify Jira input parsing
• Install via npx skills add redhat-developer/rhdh-skill --skill bug-fix and verify trigger phrases
• Test raise-pr with a Jira key: verify branch name, commit trailer, PR body, and post-PR Jira comment
• Test bug-fix with an RHDHBUGS issue: verify full workflow including screenshot capture, test plan generation, GIF upload, and PR creation with embedded images

[its-mitesh-kumar]

Raise PR Test : redhat-developer/rhdh-plugins#3708 (comment)

[durandom]

Review

Ambitious PR adding two full skills (`raise-pr` + `bug-fix`) that automate the PR lifecycle and end-to-end bug fixing with Playwright recordings. The architecture is well-thought-out — `bug-fix` chains into `raise-pr` with a clean caller-context contract.

What's good

• Repo profiles (`repo-profiles.md`) — auto-detection via `git remote -v` with separate templates for rhdh-plugins vs community-plugins is practical
• Baseline diffing — capturing `git status --porcelain` before builds to filter out pre-existing dirty files in Step 7 is clever and prevents accidental staging of unrelated changes
• Video recording workflow — the principled approach (write repro test → fail → capture before → fix → pass → capture after) with hard gates at each step prevents out-of-order execution
• GitHub Contents API for GIF upload — embedding recordings directly in the PR description via branch-committed files that auto-delete on merge is clean
• Jira input parsing (`jira-input.md`) — handles all common input formats (bare key, browse URL, URL without scheme, URL with query params)
• Changeset generation rules — correctly scoping to `plugins/` only, ignoring `packages/`, and checking published paths is right

Issues

1. Cursor-specific references. Several places reference Cursor-specific constructs:

   • `CallMcpTool: server="user-jira"` in Step 11 — not portable to Claude Code or other agents
   • `required_permissions: ["all"]` in `preflight_system_limits` — Cursor Shell tool concept
   • The Prerequisites mention "Cursor" specifically for MCP setup

   Consider abstracting the MCP calls behind a generic pattern (e.g., "use your agent's Jira MCP tool to add a comment") and noting Cursor as one implementation option.

2. PR size. Two full skills (700+ lines of SKILL.md each) plus 3 reference files in one PR is a lot to review. If this hasn't been through internal testing yet, consider splitting `raise-pr` into its own PR — it's independently useful and simpler to validate. `bug-fix` can follow as a separate PR that chains into it.

3. `workspace-map.md` will go stale. The Jira Component → workspace mapping is hardcoded. Consider generating this from the workspace directories + some metadata, or at least noting a date/version.

4. `ulimit -n 65536` in principles. This is macOS-specific (Linux typically has higher defaults). The principle should note this is primarily for macOS development.

5. Version conflict. This bumps 0.6.1 → 0.7.0. PR #58 also bumps 0.6.1 → 0.7.0. If both need to be v0.7.0 (minor for new skills), only one can merge with that version.

Recommendation

The skills are well-designed. Address the Cursor-specific portability concerns and consider splitting into two PRs for easier review. Needs version coordination with #58.