testing-workflow
Meta-skill that orchestrates comprehensive testing across a project by coordinating testing-patterns, e2e-testing, and testing agents. Use when setting up testing for a new project, improving coverage for an existing project, establishing a testing strategy, or verifying quality before a release.
Why use this skill?
Orchestrate end-to-end testing strategies with the OpenClaw testing-workflow skill. Improve coverage, establish quality gates, and automate your QA processes.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/wpank/testing-workflowWhat This Skill Does
The testing-workflow skill acts as a high-level orchestrator for project-wide software quality assurance. Rather than performing simple unit tests, this meta-skill manages the lifecycle of your testing strategy. It coordinates specialized skills like testing-patterns and e2e-testing to ensure that every layer of your application—from granular unit functions to critical user-facing flows—is verified. It acts as an expert QA lead that assesses the current codebase, identifies gaps in coverage, and directs the implementation of industry-standard testing architectures.
Installation
To integrate this skill into your environment, run the following command in your terminal:
clawhub install openclaw/skills/skills/wpank/testing-workflow
Ensure you have the required sub-skills (testing-patterns and e2e-testing) installed as well to allow the orchestrator to delegate effectively.
Use Cases
- Brownfield Projects: Ideal for retrofitting testing into legacy codebases where you need to establish a baseline before refactoring.
- Greenfield Projects: Perfect for defining a robust testing culture from day one, ensuring that infrastructure for unit, integration, and E2E testing is baked in.
- Quality Audits: Use this skill during code reviews or before major releases to verify that test coverage meets your team's threshold and that critical business logic remains protected.
- Onboarding: Helps new developers understand the testing expectations of a project by automating the discovery of existing test patterns.
Example Prompts
- "@OpenClaw testing-workflow: Scan our current codebase, create a baseline report of our unit test coverage, and suggest a testing strategy for our new microservices architecture."
- "@OpenClaw testing-workflow: We are approaching a major release. Please audit our current test suite for skipped or flaky tests and verify that our critical checkout flow is fully covered by E2E tests."
- "@OpenClaw testing-workflow: I'm adding a new feature to our payments module. Orchestrate the necessary steps to implement test-driven development for this component."
Tips & Limitations
- Baseline First: Never skip the Phase 1 Discovery step. Without an accurate baseline, the AI cannot verify if your new tests actually improve project health.
- Human Oversight: While the skill automates orchestration, the final review of coverage targets and critical user journeys should always involve a project lead to ensure business context is captured.
- Dependency Management: Ensure your CI/CD configuration is accessible to the agent, as the skill relies on reading these files to map the existing infrastructure accurately.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-wpank-testing-workflow": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, file-write, code-execution
Related Skills
mermaid-diagrams
Create software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams, sequence diagrams, flowcharts, ERDs, C4 architecture diagrams, state diagrams, git graphs, and other diagram types. Triggers include requests to diagram, visualize, model, map out, or show the flow of a system.
api-design-principles
Skill by wpank
auto-context
Automatically read relevant context before major actions. Loads TODO.md, roadmap.md, handoffs, task plans, and other project context files so the AI operates with full situational awareness. Use when starting a task, implementing a feature, refactoring, debugging, planning, or resuming a session.
clear-writing
Write clear, concise prose for humans — documentation, READMEs, API docs, commit messages, error messages, UI text, reports, and explanations. Combines Strunk's rules for clearer prose with technical documentation patterns, structure templates, and review checklists.
track-performance
Track the performance of Uniswap LP positions over time — check which positions need attention, are out of range, or have uncollected fees. Use when the user asks how their positions are doing.