replicate-issue
Best for QA engineers validating bug…Works with GitHub
⌘source
- author
@coleam00- repo
- coleam00/Archon
- language
- TypeScript
★19kstars
2.9kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Systematically tests all described symptoms using browser automation
- ·Checks out main branch and pulls latest code
- ·Produces findings report with reproduction steps
- ·Validates GitHub issues against live Archon application
- ·Identifies related issues and provides fix recommendations
Use Cases
- →Reproducing a bug reported in a GitHub issue
- →Validating whether a reported problem is real before working on a fix
- →Confirming bug existence for quality assurance
- →Investigating issue symptoms systematically
Best for
- ✓QA engineers validating bug reports
- ✓Developers confirming issues before fixing
- ✓Teams needing systematic bug reproduction
Not ideal for
- !Fixing issues (use /archon or /exp-piv-loop:fix-issue)
- !General UI testing (use /validate-ui)
- !One-off manual testing
FAQs
name
replicate-issue
description
Replicate and validate a GitHub issue by spinning up Archon, analyzing the issue,
and systematically testing all described symptoms using browser automation.
Use when: User wants to reproduce a bug, validate a GitHub issue, confirm a reported problem,
or investigate whether an issue is real before working on a fix.
Triggers: "replicate issue", "reproduce issue", "validate issue", "confirm bug",
"test issue", "can you reproduce", "try to replicate", "verify the bug".
Capability: Checks out main, pulls latest, starts Archon, reads the GitHub issue,
then uses agent-browser to systematically test every symptom and produce a findings report.
NOT for: Fixing issues (use /archon or /exp-piv-loop:fix-issue), general UI testing (use /validate-ui).
argument-hint:[issue-number]
disable-model-invocation:true
allowed-tools:Bash, Read, Grep, Glob, WebFetch, Agent
Replicate GitHub Issue
Systematically reproduce and validate a GitHub issue against the live Archon application. The goal: determine whether the reported behavior is real, identify exact reproduction steps, discover any related issues, and provide actionable fix recommendations.
Issue number: $ARGUMENTS
If $ARGUMENTS is empty, ask the user for the issue number before proceeding.
Phase 0: Prepare Environment
0.1 Switch to Main Branch and Pull Latest
Ensure you are testing against the latest code on main so results are accurate.
cd /path/to/archon
# Stash any local changes to avoid conflicts
git stash 2>/dev/null || true
# Switch to main and pull latest
git checkout main
git pull origin main
echo "On branch: $(git branch --show-current)"
echo "Latest commit: $(git log --oneline -1)"
0.2 Kill Existing Archon Processes
Free up ports 3090 (backend) and 5173 (frontend) so Archon starts cleanly.
pkill -f "bun.*dev:server" 2>/dev/null || true
pkill -f "bun.*dev:web" 2>/dev/null || true
pkill -f "bun.*packages/server" 2>/dev/null || true
pkill -f "bun.*packages/web" 2>/dev/null || true
fuser -k 3090/tcp 2>/dev/null || true
$install
1-click copynpx skills add coleam00/Archon --skill replicate-issueSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.