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.
Best use case
qa-check is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using qa-check should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/qa-check/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How qa-check Compares
| Feature / Agent | qa-check | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
```bash
# 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
```bash
# 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
```bash
# 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
| Check | Tool | Pass Criteria |
|-------|------|---------------|
| Build | `npm run build` | Exit 0, no errors |
| Browser | `browser snapshot` | No console errors |
| Mobile | `browser screenshot` | Readable, no scroll |
| Links | `curl` | All 200/301 |
| Speed | Browser | < 3s load |
| SEO | Read index.html | All 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.Related Skills
security-check
Voer geautomatiseerde security checks uit op codebases. Scant broncode, configuraties en dependencies op kwetsbaarheden met Semgrep, Trivy en Gitleaks. Categoriseert findings per OWASP Top 10 met genormaliseerde severity levels. Gebruik bij security scans, PR reviews, of compliance checks.
pyright-type-checker
Pyright fast Python type checker from Microsoft with VS Code integration and strict type checking modes
ln-774-healthcheck-setup
Configures health check endpoints for Kubernetes readiness/liveness/startup
health-check
Check health status of all running services and dependencies. Use when verifying services are running, debugging connectivity issues, or monitoring system status.
gradle-dependency-checker
Executes Gradle dependency check commands, retrieves and analyzes dependency trees, and extracts version information for key dependencies such as kotlin/kotlinx/skiko/androidx. Use when users need to check Gradle project dependency versions or analyze dependency relationships.
entry-point-check
验证 VS 的 entry_points 字段是否与 SPEC_PRJ_ENTRYPOINTS(入口类型标签)一致,生成缺失入口清单和补充建议。当准备 CONSTRAINT 验收前使用。
debug-validator-checkpoint-inconsistency
Debug validator checkpoint inconsistencies where some validators are behind others. Use when alerts mention "checkpoint inconsistency", "validators behind", or "inconsistent latest checkpoints", or when asked to debug validator sets, investigate validator delays, or troubleshoot metadata fetch failures for a chain. Defaults to default_ism app context if not specified.
code-review-checklist
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability
checkstyle-rules
Use when applying Checkstyle built-in checks for Java code including naming conventions, code metrics, and suppressions.
checklist-generator
Generate context-aware quality checklists for code review and QA using IEEE 1028 base standards plus LLM contextual additions
checking-quality
Ensures code quality through comprehensive checks including TDD practices, lint/test/build validation, and prevention of common mistakes. Use after completing implementations, fixing bugs, refactoring, or before committing code.
chatgpt-apps-production-checklist
Turn ChatGPT Apps implementation work into a production-ready checklist with concrete tasks, tests, widget changes, and tool-result patterns mapped by priority (P0/P1/P2). Use when designing or hardening Apps SDK products for shipping; do not use for generic web-only apps, static code review, or non-ChatGPT integration planning.