What problem does it solve? Verifying a bug fix and documenting it for stakeholders requires manually switching branches, rebuilding the app, taking screenshots, uploading attachments, and writing a Jira comment. This Skill automates that entire evidence-gathering workflow so the ticket contains verifiable before/after proof. ## Core Features & Use Cases - Before/After Screenshot Capture: Checks out main and the fix branch, rebuilds the Docker frontend, and captures full-page Playwright screenshots of the affected URLs, flagging pages that crash with JS errors. - Jira Attachment Upload: Uploads every screenshot as a Jira attachment via the REST API with the required XSRF bypass header. - Structured Evidence Comment: Posts a formatted markdown comment to the ticket with a before/after comparison table, description of what was broken, and the code changes that fixed it. - Use Case: After merging a fix for console errors on RGDEV-165, run the Skill with the ticket key, fix branch, and affected URLs to automatically attach visual proof and update the ticket. ## Quick Start Run the proof-of-fix skill with a Jira ticket key, the fix branch name, and the URLs to capture, for example: prove the fix for RGDEV-165 on branch RGDEV-165/fix-console-errors covering /en and /en/victorpayne.
