qa-lead

What This Skill Does

The qa-lead skill transforms your OpenClaw agent into a seasoned Quality Assurance Lead with over a decade of industry experience. It provides a structured, phase-based framework for managing the entire software testing lifecycle, from initial strategy design to the implementation of automated testing suites and CI/CD quality gates. By leveraging this skill, you ensure that every line of code is backed by a robust testing strategy, adhering to best practices in unit, integration, and end-to-end (E2E) testing. The skill enforces a granular approach, preventing information overload by breaking down large test suites into manageable, single-file increments. It integrates seamlessly with industry-standard tools like Playwright and Jest, ensuring your projects maintain a minimum of 80% test coverage on critical paths.

Installation

To integrate this expert QA functionality into your environment, execute the following command in your terminal within the OpenClaw directory:

clawhub install openclaw/skills/skills/anton-abyzov/sw-qa-lead

This command pulls the latest stable version from the official repository, ensuring you have access to the latest test automation patterns and configuration templates.

Use Cases

• Establishing Test Strategy: Quickly draft comprehensive test plans for new features by referencing built-in templates.
• Automation Scaling: Generate production-ready Playwright and Jest test suites that map directly to your project's Acceptance Criteria.
• Quality Gate Integration: Define and implement automated quality gates within CI pipelines to prevent regressions from reaching production.
• Test Coverage Audits: Maintain strict adherence to organizational quality standards by systematically tracking TC (Test Case) IDs against user stories.

Example Prompts

1. "I am starting a new authentication feature. Please initialize the test strategy phase and help me map out the initial test cases based on my provided ACs."
2. "Generate the Playwright E2E test file for the checkout flow, focusing on the payment validation logic."
3. "Review the current coverage metrics and help me create a quality gate configuration for our GitHub Actions pipeline to block deployments under 80% coverage."

Tips & Limitations

• Always verify one file at a time: The skill is optimized for precision. Requesting too much code in a single turn will dilute the quality of the generated tests.
• Map to ACs: Never generate a test that doesn't link back to a specific requirement or Acceptance Criterion. This ensures maintainability.
• Token Budgeting: Keep your prompts concise. If a feature is complex, perform the analysis phase first before triggering the generation phases to stay within the recommended token budgets. The skill is designed to manage context memory by modularizing large suites into distinct files, so embrace the 'one file per response' workflow to ensure the AI remains focused and accurate.