skills.rest
Youngger9765
Youngger9765COMMUNITY
Explore all skills by this author →
GitHub

quick-verify

Verifies frontend bug fixes in Chrome and logs findings to GitHub Issues.

Updated Aug 23, 2026
Search Tags:#testing#frontend#staging#github issues#bug verification#mcp chrome
One-click install
npx skills add https://github.com/Youngger9765/career-creator --skill quick-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quick-verify
Source: https://github.com/Youngger9765/career-creator/tree/main/.claude/skills/quick-verify
Command: npx skills add https://github.com/Youngger9765/career-creator --skill quick-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a rapid, standardized method for verifying frontend bugs in the MCP Chrome browser, ensuring quick validation of fixes before escalating to more complex testing.

Core Features & Use Cases

  • Rapid Bug Triage: Quickly confirm if a fix is deployed and effective on staging or localhost.
  • Standardized Reporting: Ensures all verification steps, including screenshots and root cause analysis, are logged to GitHub Issues.
  • Use Case: A developer pushes a fix for a visual bug. You use /quick-verify {issue_number} to immediately check the fix on staging, capture before/after screenshots, and log the findings to the issue.

Quick Start

Use the quick-verify skill with the issue number to verify a frontend bug.

Frequently Asked Questions about quick-verify

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

FAQPage Schema
How do I verify a frontend bug fix on staging?▼

To verify a frontend bug fix on staging, you can automate the reproduction process using the MCP Chrome browser to validate the deployment and capture mandatory screenshots as evidence.

Can I automate frontend bug verification and log findings to GitHub Issues?▼

Yes, you can automate frontend bug verification to reproduce issues in MCP Chrome and directly log all findings, screenshots, and root cause analysis to GitHub Issues.

How do I capture verification screenshots for a localhost bug?▼

You can capture verification screenshots for a localhost bug by running automated checks in the MCP Chrome browser, which mandates screenshot capture and evidence archiving before logging.

Does frontend bug verification require strict documentation for issue comments?▼

Yes, frontend bug verification requires adherence to strict documentation rules for issue comments to ensure standardized reporting of steps, screenshots, and root cause analysis.

What is the best way to perform rapid bug triage for frontend visual issues?▼

The best way to perform rapid bug triage for frontend visual issues is to automate the reproduction process to quickly confirm if a deployed fix is effective on staging or localhost.

Related Skills

Explore More Software Engineering Skills→
zillafan80-Maxzillazillafan80-Maxzilla

archon-replicate-issue

Reproduce and validate GitHub issues using Archon and browser automation.

Community
Advanced
dakshrawat298-gifdakshrawat298-gif

security-fix-review

Review security patches for root-cause coverage and bypass risks.

Community
Intermediate
vrcmsvrcms
1

browser-qa

Automate visual testing and UI interaction verification for web applications.

Community
Advanced
misty-stepmisty-step
2

qa

Coordinates automated Playwright and manual QA routes with evidence capture for bug reports.

Official
Advanced