qa-check

What This Skill Does

The qa-check skill is a comprehensive, mandatory quality assurance framework designed for OpenClaw AI agents to ensure that all development work meets production standards before deployment. It acts as a gatekeeper, systematically validating build integrity, browser-side functionality, mobile responsiveness, link health, performance metrics, and SEO metadata. By automating the verification process, it removes human error from the deployment checklist, ensuring that every project shared or deployed to production is functional, optimized, and error-free.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/gizmo-dev/qa-check Once installed, ensure your project directory contains the necessary configuration scripts, or initialize the standard scripts/qa-check.sh entry point provided by the source repository.

Use Cases

This skill is essential in several scenarios:

1. Continuous Deployment: Run it automatically via CI/CD pipelines before any vercel --prod deployment.
2. Pre-Launch Validation: Use it before sharing project URLs on social media or with clients to prevent "link rot" or broken designs.
3. Skill Development: Utilize it before publishing new skills to the ClawHub to maintain high community standards.
4. Refactoring Checks: Invoke it after major architectural changes or dependency updates to ensure that core functionality remains intact.

Example Prompts

1. "Run the qa-check for the project located in the current directory and report any failures before I push to production."
2. "Perform a full QA suite on my latest build, specifically focusing on mobile responsiveness and external link validation."
3. "My project is ready for deployment; can you execute the qa-check skill and summarize the build validation and SEO meta results?"

Tips & Limitations

• Tip: Treat the failure criteria as a hard stop. If the skill identifies a failure, do not attempt to bypass it; the cost of a buggy production release is significantly higher than the time required for a fix.
• Tip: Regularly audit your scripts/qa-check.sh to ensure it reflects the latest project dependencies.
• Limitation: The skill performs static and automated dynamic checks. While it verifies link status and layout, it cannot simulate complex business logic or user intent; human verification of final production deployment remains the final step.