replicate-issue

Reproduce and validate GitHub issues using Archon and browser automation.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/az9713/Archon-tutorial --skill replicate-issue-az9713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: replicate-issue
Source: https://github.com/az9713/Archon-tutorial/tree/main/.claude/skills/replicate-issue
Command: npx skills add https://github.com/az9713/Archon-tutorial --skill replicate-issue-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replicate and validate a GitHub issue by spinning up Archon, analyzing the issue, and systematically testing all described symptoms using browser automation.

Core Features & Use Cases

  • Systematic reproduction of reported symptoms against a live application.
  • Automated test planning, evidence collection, and findings reports.
  • Guided browser interactions via agent-browser to verify behavior and document results.

Quick Start

Provide the GitHub issue number to start the automated replication workflow.

Frequently Asked Questions about replicate-issue

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

FAQPage Schema
How do I reproduce a GitHub issue automatically using browser automation?

To reproduce a GitHub issue, provide the issue number to trigger an automated workflow that orchestrates Archon to analyze symptoms and execute deterministic browser-based verification against the live application.

What is the best way to verify reported bug symptoms against a live application?

The best way to verify reported bug symptoms is using Archon-orchestrated browser automation, which applies deterministic test planning and execution to systematically validate the described behavior and document results.

How does automated test planning work for GitHub issue reproduction?

Automated test planning for GitHub issue reproduction works by analyzing the issue details to generate deterministic browser interactions, executing guided test steps, and collecting evidence to confirm the reported symptoms.

Do I need Archon-enabled tooling to validate GitHub bug reports?

Yes, you need Archon-enabled tooling to validate GitHub bug reports, as it provides the required agent-browser interactions to perform test planning, execute verification steps, and generate findings reports.

Can I gather evidence to support fixes for a GitHub bug report?

Yes, you can gather evidence to support fixes by running automated browser verification that reproduces the issue, validates the reported symptoms, and outputs a documented findings report with the collected test results.

What limitations exist when replicating issues with deterministic browser-based verification?

A key limitation of deterministic browser-based verification is that it requires access to complete GitHub issue details and a live application environment to successfully reproduce symptoms and generate accurate findings reports.