qa-quality-gateQA lead skill for evidence review, gate enforcement, release-readiness assessment, and quality signoff recommendations.
Install via ClawdBot CLI:
clawdbot install aiweline/qa-quality-gateGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 23, 2026
A development team completes a new feature and submits test evidence for QA review. The skill evaluates unit, HTTP, E2E, and WLS gates, identifies missing coverage, and provides a release-readiness recommendation to the Technical Lead.
After a bug fix, the QA lead uses this skill to check that regression tests were run on the affected surface, validates runtime logs, and rejects insufficient evidence. The skill ensures that the fix is properly validated before signoff.
When an API interface changes, the skill verifies that the corresponding documentation is updated. It fails the gate if docs are missing, preventing undocumented changes from being released.
For a release with known but acceptable risks, the skill produces a conditional signoff, documenting each residual risk and the conditions for release. This enables informed decision-making by the Technical Director.
When multiple teams contribute to a release, the skill consolidates evidence from each team, checks all required gates, and identifies cross-team validation gaps. It ensures that no team's work is signed off without proper evidence.
Offer a gate enforcement service to development teams or clients, ensuring that releases meet quality standards before deployment. The skill automates evidence review and signoff recommendations.
Integrate this skill into CI/CD pipelines to automatically evaluate quality gates on every build or release candidate. This reduces manual QA overhead and accelerates release cycles.
Provide expert consulting to organizations needing robust quality gate processes. Use the skill to audit existing practices, train teams, and set up automated gate checks.
💬 Integration Tip
Integrate with CI/CD tools like Jenkins or GitLab Actions to trigger gate checks automatically on merge requests or release branches.
Scored May 23, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.