frontend-bug-review

Reviews Express SSR frontend code for template, interaction, and auth defects with regression tests.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/werlang/event-hub --skill frontend-bug-review-werlang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-bug-review
Source: https://github.com/werlang/event-hub/tree/main/.agents/skills/frontend-bug-review
Command: npx skills add https://github.com/werlang/event-hub --skill frontend-bug-review-werlang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend bugs in server-rendered apps often hide in the seams between Mustache templates, route wiring, client bundles, and API responses, and they slip through when reviews focus only on style. This Skill provides a disciplined audit workflow for the Academic Events web/ app that finds real user-facing defects and locks them down with deterministic tests. ## Core Features & Use Cases - Contract Mismatch Detection: Finds mismatches between HTML ids/classes, JS selectors, SSR template variables, route output, and checked-in bundles. - Flow-Level Bug Hunting: Targets query-state hydration, URL sync, login redirects, token persistence, modal/tab state, and datetime normalization issues. - Regression Coverage Pairing: Maps each finding to the right test type (pure helper, jsdom plus VM, spawned route test, or browser pass) under web/tests. - Use Case: When a dashboard filter stops syncing to the URL or a login redirect misbehaves, use this Skill to trace the flow from SSR shell to client boot, prove the defect, and add a failing-then-passing test. ## Quick Start Review the week page frontend for query-state and date rendering bugs, then add matching regression tests under web/tests.

Frequently Asked Questions about frontend-bug-review

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

FAQPage Schema
How do I review SSR frontend code for bugs?▼

Trace each user flow from the SSR shell through client boot to API handling, then compare HTML ids, JS selectors, template variables, and route output for mismatches. Prioritize defects that change user behavior, UI state, or submitted data over style feedback.

How to test Express Mustache template rendering?▼

Use spawned Express route checks to assert SSR rendering, template variables, static bundle inclusion, and page-shell contracts. For client-side behavior, use jsdom plus VM entrypoint tests that exercise DOM mutations and event wiring.

When do frontend bugs need real browser testing?▼

Browser validation is needed when behavior depends on actual clicks, typing, focus timing, CSS layout, localStorage or sessionStorage persistence, redirects, or authenticated multi-step flows. Deterministic jsdom tests cover the rest.

Why do datetime-local inputs cause timezone bugs?▼

datetime-local values lack timezone information, so submitting them without ISO normalization or rendering them without local week-range awareness causes drift. Normalize values to ISO payloads and verify rendered labels against local date boundaries.

What are the limitations of automated frontend review?▼

Automated review cannot fully verify responsive layout, real focus behavior, or cross-service authenticated flows, which require manual browser passes. It also avoids style-only feedback and speculative redesigns without concrete behavior risk.