qa-check

Mandatory quality assurance for all dev work before publishing. Use BEFORE deploying any project to production. Validates build, tests browser functionality, checks mobile responsiveness, and ensures no broken links/images.

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "qa-check" with this command: npx skills add gizmo-dev/qa-check

QA Check

Mandatory pre-deployment quality assurance. Run this before ANY project goes live.

When to Use

  • Before vercel --prod or any production deploy
  • Before announcing/sharing any project URL
  • Before publishing skills to ClawHub
  • After major code changes

QA Checklist

1. Build Validation

# Ensure build succeeds without errors
cd <project-dir>
npm run build

Fail criteria: Build errors, warnings about missing dependencies

2. Browser Functional Test

Use browser tool to verify:

  • Page loads without console errors
  • All interactive elements work (buttons, links, forms)
  • No broken images (check Network tab for 404s)
  • No JavaScript errors in console
browser snapshot → check for errors
browser console → verify no red errors

3. Mobile Responsiveness

browser screenshot --mobile

Check:

  • Content readable on mobile viewport
  • No horizontal scroll
  • Buttons/links tappable (not too small)
  • Navigation works

4. Link Validation

# Check all external links resolve
grep -r "href=" src/ | grep -o 'https://[^"]*' | sort -u | while read url; do
  curl -s -o /dev/null -w "%{http_code} $url\n" "$url"
done

5. Performance Quick Check

  • Page loads in < 3 seconds
  • No massive bundle warnings (> 500KB)
  • Images optimized (not raw screenshots)

6. SEO/Meta Basics

Verify in index.html:

  • <title> set (not generic)
  • <meta name="description"> present
  • <meta property="og:*"> for social sharing
  • Favicon present

Pre-Deploy Command

# Run full QA suite
scripts/qa-check.sh <project-dir>

Fail = No Deploy

If ANY check fails:

  1. Document the issue
  2. Fix it
  3. Re-run QA
  4. Only then deploy

Quick Reference

CheckToolPass Criteria
Buildnpm run buildExit 0, no errors
Browserbrowser snapshotNo console errors
Mobilebrowser screenshotReadable, no scroll
LinkscurlAll 200/301
SpeedBrowser< 3s load
SEORead index.htmlAll meta present

Post-Deploy Verification

After deploy, ALWAYS:

  1. Visit production URL in browser
  2. Click through main features
  3. Check mobile view
  4. Verify analytics loading (if added)

Only THEN announce/share the project.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

Sharedintellect Quorum

Multi-agent validation framework — 6 independent AI critics evaluate artifacts against rubrics with evidence-grounded findings.

Registry SourceRecently Updated
7960Profile unavailable
Automation

Score Agent Response Quality

Score an AI agent response 0-100 across 6 quality dimensions (depth, recommendations, citations, formatting, trust, monetization-readiness) with improvement...

Registry SourceRecently Updated
990Profile unavailable
Security

Test Master

Use when you need a practical testing playbook for turning product or code changes into a clear test strategy, test cases, and execution checklist.

Registry SourceRecently Updated
1650Profile unavailable
Automation

Canary

Safety monitoring and tripwire detection for AI agents. Protects against unauthorized file access, dangerous commands, and excessive activity. Auto-halts on...

Registry SourceRecently Updated
4480Profile unavailable