skills.rest
ahliweb
ahliwebCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

repro-public

Reproduce public-site rendering bugs in the anonymous visitor experience.

Updated Aug 23, 2026
Search Tags:#debugging#screenshots#astro#bug reproduction#agent-browser#public site
One-click install
npx skills add https://github.com/ahliweb/sikesra --skill repro-public-ahliweb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repro-public
Source: https://github.com/ahliweb/sikesra/tree/main/awcmsmicro-dev/.flue/skills/repro-public
Command: npx skills add https://github.com/ahliweb/sikesra --skill repro-public-ahliweb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reliably reproduce and document bugs in the public-facing site so maintainers can see the exact broken behavior without needing an admin login.

Core Features & Use Cases

  • Browser-only reproduction: Open the affected public route in agent-browser and observe the real rendered output a visitor sees.
  • Evidence capture: Save screenshots, inspect the accessibility tree, and record console or runtime errors for a precise report.
  • Replayable notes: Document the URL, query string, locale, and interaction sequence so someone else can repeat the bug exactly.

Quick Start

Use this skill to start the demo, open the affected public URL in agent-browser, and capture screenshots plus a transcript of the failure.

Frequently Asked Questions about repro-public

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

FAQPage Schema
How do I reproduce a public site rendering bug in Astro with screenshots?▼

You can reproduce a public site rendering bug by opening the affected Astro route in agent-browser, capturing screenshots, inspecting the DOM slice, and recording console errors. This verifies the exact visitor experience.

How do I document Astro sitemap or RSS output errors for maintainers?▼

To document Astro sitemap or RSS output errors, record the URL, query string, and interaction sequence alongside screenshots and console logs. This creates a replayable transcript for maintainers to verify.

Do I need an admin login to debug public routing bugs?▼

You do not need an admin login to debug public routing bugs. Browser-only reproduction isolates the anonymous visitor experience, capturing evidence like accessibility tree snapshots and runtime errors without admin access.

What is the best way to capture evidence of query-dependent rendering failures?▼

The best way to capture evidence of query-dependent rendering failures is using agent-browser verification. It records the query string, takes screenshots, and logs console errors for a precise, replayable bug report.

Can I use agent-browser to inspect image rendering issues on public pages?▼

Yes, you can use agent-browser to inspect image rendering issues on public pages. It captures the real rendered output visitors see, allowing you to document broken images with screenshots and DOM slices.

Related Skills

Explore More Software Engineering Skills→
emdash-cmsemdash-cms
11.6k

repro-public

Reproduce public-site rendering bugs via bgproc demo and agent-browser.

Official
Advanced
RemseyMailjardRemseyMailjard

github-issue-creator

Convert messy bug notes and logs into structured GitHub issue markdown files.

Community
Intermediate
RxFitRxFit

browse

Automate headless browser interactions to verify web pages and test user flows.

Community
Advanced
AkbarDevopAkbarDevop

canary

Monitor live web applications for console errors and page failures post-deployment.

Community
Advanced