replicate-issue

Replicate GitHub issues by testing symptoms with browser automation.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/RsultCoding/rca-archon --skill replicate-issue-rsultcoding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: replicate-issue
Source: https://github.com/RsultCoding/rca-archon/tree/main/.claude/skills/replicate-issue
Command: npx skills add https://github.com/RsultCoding/rca-archon --skill replicate-issue-rsultcoding

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

  • Systematically reproduce a GitHub issue against the live Archon application.
  • Analyze issue details to build a clear reproducibility plan and test plan.
  • Use agent-browser to execute end-to-end browser interactions, capture evidence, and generate a findings report.

Quick Start

Provide an issue number to start reproducing and validating the reported GitHub issue.

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 against a live Archon application?

Yes, browser automation is required for reproducing the GitHub issue. The skill uses agent-browser to execute end-to-end browser interactions against the live Archon application, capturing evidence of the reported symptoms and generating a validation findings report.

How do I validate reported GitHub issues using browser automation?

Validating a GitHub issue involves analyzing the issue details to build a clear reproducibility plan and test plan. The skill then uses agent-browser to execute end-to-end browser interactions against the live Archon application, capturing evidence and generating a findings report.

What is the process to systematically test GitHub issue symptoms in Archon?

Systematically testing GitHub issue symptoms in Archon involves checking out main, pulling the latest code, and starting the application. The skill then reads the GitHub issue and uses agent-browser to test each described symptom, generating a comprehensive findings report.

Can I investigate GitHub issue feasibility across a live Archon instance?

Yes, you can investigate GitHub issue feasibility across a live Archon instance. By providing the issue number, the skill spins up Archon, uses browser automation to test the reported problem, and confirms whether the issue is reproducible with a findings report.

Do I need to provide an issue number to start reproducing a GitHub bug?

Yes, you need to provide a GitHub issue number to start reproducing and validating the reported problem. This allows the skill to read the issue details, build a test plan, and execute browser automation against the Archon application.