dx-bug-verify

Automate bug reproduction and verification across environments using Chrome DevTools MCP.

6|3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-bug-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dx-bug-verify
Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-core/skills/dx-bug-verify
Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-bug-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproducing and verifying software bugs across different environments is slow and error-prone. This Skill automates end-to-end bug verification by reading spec docs (raw-bug.md and optional triage.md), driving Chrome DevTools MCP to execute repro steps, collecting evidence, and producing a structured verification report for Azure DevOps or Jira.

Core Features & Use Cases

  • Automatically extracts repro steps and expected vs actual behavior from raw-bug.md (and triage.md if present) and orchestrates Chrome DevTools actions to reproduce the bug.
  • Supports before, after, and qa modes to cover pre-fix verification, local post-fix checks, and post-merge QA validation.
  • Generates and saves mode-specific verification files (verification.md, verification-local.md, verification-qa.md) with screenshots, console logs, and diagnostics, and posts results back to the relevant work item.

Quick Start

Execute dx-bug-verify with a Bug ID to start automated reproduction against the configured environment.

Frequently Asked Questions about dx-bug-verify

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

FAQPage Schema
How do I automate bug reproduction and verification using Chrome DevTools?

Automated bug reproduction uses Chrome DevTools MCP to execute repro steps extracted from raw-bug.md and triage.md, collecting console logs and screenshots to generate a structured verification report.

Can I integrate automated bug verification with Azure DevOps or Jira work items?

Yes, bug verification integrates directly with Azure DevOps and Jira, automatically posting the generated verification results and evidence back to the relevant work item for review and handoff.

What is the difference between before, after, and qa modes in bug verification?

Bug verification modes cover pre-fix verification, local post-fix checks, and post-merge QA validation, generating mode-specific files like verification.md, verification-local.md, and verification-qa.md.

How do I extract repro steps and expected behavior for automated bug testing?

Automated bug testing extracts repro URLs, repro steps, and expected versus actual behavior directly from raw-bug.md and optional triage.md spec docs to orchestrate Chrome DevTools actions.

Does automated bug verification support config-driven URL handling and authentication?

Yes, automated bug verification supports config-driven URL handling and authentication to drive Chrome DevTools workflows across different environments and reproduce bugs accurately.

What evidence is collected during automated bug reproduction?

Bug reproduction collects screenshots, console logs, and diagnostics via Chrome DevTools MCP, saving this evidence into mode-specific verification files for structured review.