otgruzka-browser-verify

Verifies UI bug fixes on the production Vercel deployment using browser checks and console inspection.

Updated May 5, 2026
One-click install
npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill otgruzka-browser-verify-nikegeorgian-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: otgruzka-browser-verify
Source: https://github.com/nikegeorgian-stack/otgruzka-tovara/tree/main/.cursor/skills/otgruzka-browser-verify
Command: npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill otgruzka-browser-verify-nikegeorgian-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents false "fixed" claims by requiring verification of bugs and UI changes on the canonical production deployment (Vercel) instead of a local dev server, where bundles, data, and behavior can differ. ## Core Features & Use Cases - Production-Only Verification: Enforces testing against the live Vercel URL with hard refresh, correct role login, and matching month/employee context. - Structured Checklist: Covers preparation, bundle hash confirmation, on-screen UI checks, console error review, and strict data-safety rules (no seeding or overwriting production data). - Standardized Verdict Format: Produces a PASS / FAIL / BLOCKED report with URL, bundle, role, observations, and console errors. - Use Case: After fixing a timesheet UI bug and deploying, a user reports it still fails. The Skill walks through logging in as the correct role on production, reproducing the scenario, checking console errors, and issuing a FAIL verdict with evidence instead of assuming the fix worked. ## Quick Start Verify on the production Vercel site whether the reported Otgruzka bug is actually fixed and give me a PASS, FAIL, or BLOCKED verdict.

Frequently Asked Questions about otgruzka-browser-verify

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

FAQPage Schema
How do I verify a bug fix on a production Vercel deployment?▼

Open the canonical Vercel URL with a hard refresh (Ctrl+F5), log in under the role matching the reported symptom, reproduce the exact scenario, and check the console for errors. Conclude with a PASS, FAIL, or BLOCKED verdict including URL, bundle hash, and observations.

Why does a fix work locally but not on production?▼

Local dev servers use different bundles and data than production. Common causes are stale browser cache, undeployed code, different hosting targets serving different bundles, or mismatched month, role, or employee data between environments.

Should I test on Firebase Hosting or the Vercel deployment?▼

Test on the canonical Vercel URL, since the Firebase Hosting mirror can serve a different bundle. The Vercel deployment is the source of truth for what users actually see.

Can I modify production data to reproduce a bug?▼

No. Verification is read-only by default: never seed, import, or overwrite production data to make it match local state. Test edits are allowed only with explicit user permission and must be reported in the verdict.

What should I do when I cannot access production to verify?▼

Report a BLOCKED verdict stating exactly what is missing, such as login credentials, access rights, or data. Do not substitute local testing as proof that the issue is resolved.