replicate-issue

Replicate GitHub issues by testing symptoms in Archon and capturing evidence.

Updated May 13, 2026

Search Tags:#github #browser automation #test plan #bug reproduction #archon #issue validation #screenshot evidence

Ready to run

npx skills add https://github.com/cliffthelin/AXiomEngine --skill replicate-issue-cliffthelin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: replicate-issue
Source: https://github.com/cliffthelin/AXiomEngine/tree/main/archon/.claude/skills/replicate-issue
Command: npx skills add https://github.com/cliffthelin/AXiomEngine --skill replicate-issue-cliffthelin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify whether a reported GitHub issue is real by reproducing the bug end-to-end and capturing evidence.

Core Features & Use Cases

Issue-driven test planning: Reads the GitHub issue and converts its symptoms into a structured checklist of what to test.
Systematic reproduction: Spins up Archon on the latest main, then uses browser automation to run the reported steps exactly.
Evidence-backed findings: Captures screenshots at key points, records reproduction status, and produces a summary report with next-step recommendations.
Optional workflow triggering: Uses the backend REST API to trigger workflows and chat messages when the UI requires it.

Quick Start

Use this skill by telling the AI the GitHub issue number you want replicated, for example: “Replicate issue 1234”.

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 with browser automation and capture screenshot evidence?▼

You can reproduce a GitHub issue by spinning up Archon, reading the issue details, and using agent-browser for deterministic browser interactions to systematically test the described symptoms while capturing screenshots.

How does issue validation work for confirming reported UI bugs?▼

Issue validation works by converting GitHub issue symptoms into a structured test checklist, executing the reported steps via browser automation, cross-referencing UI with API via curl, and producing a structured replication report.

Do I need a live Archon instance to replicate GitHub issues?▼

Yes, you need a live Archon instance running on the main branch to replicate GitHub issues, as it spins up Archon to execute the systematic browser testing and workflow triggering required for validation.

Can I trigger backend REST API workflows during GitHub issue reproduction?▼

Yes, you can trigger backend REST API workflows and chat messages during GitHub issue reproduction when the UI workflow requires it, allowing you to cross-reference UI interactions with API responses via curl.

What is the best way to document bug reproduction steps for a GitHub issue?▼

The best way to document bug reproduction steps is to use browser automation to run the reported steps, capture screenshots at key points, record reproduction status, and output a summary report with next-step recommendations.

What are the limitations of using agent-browser for deterministic issue reproduction?▼

A limitation is that agent-browser requires deterministic browser interactions, meaning non-deterministic UI behaviors or intermittent bugs may not reproduce consistently, and you need a live Archon instance on main to run the validation.