openclaw-testing

Select and execute targeted Vitest suites and GitHub Actions CI lanes.

Updated Jun 18, 2026

Search Tags:#automation #testing #debugging #release #ci #openclaw

Ready to run

npx skills add https://github.com/wangqianCAI/OBI --skill openclaw-testing-wangqiancai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openclaw-testing
Source: https://github.com/wangqianCAI/OBI/tree/main/.agents/skills/openclaw-testing
Command: npx skills add https://github.com/wangqianCAI/OBI --skill openclaw-testing-wangqiancai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the inefficiency of running full test suites for minor changes by providing a structured, intelligent path to identify and execute only the necessary tests, CI checks, and release validations.

Core Features & Use Cases

Targeted Testing: Automatically determines the minimal set of Vitest targets or CI lanes required based on the touched code surface.
CI/CD Debugging: Provides a streamlined workflow for inspecting GitHub Actions runs, rerunning failed jobs, and validating release candidates.
Use Case: When a developer makes a small change to a core plugin, this Skill helps them run only the relevant plugin tests and contract checks instead of waiting for the entire repository test suite to complete.

Quick Start

Use the openclaw-testing skill to identify and run the cheapest safe test suite for the current code changes.

Frequently Asked Questions about openclaw-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run targeted Vitest suites based on code diff analysis?▼

Targeted Vitest execution uses source code diff analysis to automatically resolve and run only the minimal set of test suites required for the touched code surface, ensuring efficient regression testing without waiting for the entire repository test suite to complete.

What is the best way to debug failed GitHub Actions release validation workflows?▼

Debugging GitHub Actions release validation involves inspecting CI runs, rerunning failed jobs, and validating release candidates through a streamlined workflow to achieve production-grade release orchestration and reliable failure reproduction.

Can I use openclaw-testing to reproduce CI verification failures locally?▼

Yes, openclaw-testing supports failure reproduction by applying source code diff analysis and targeted CI verification lane selection to isolate the specific tests and checks needed to replicate the failure environment efficiently.

Does this Skill require any external dependencies to run OpenClaw CI checks?▼

No, this Skill operates without external dependencies, relying solely on its internal references component to automate CI verification lane selection and GitHub Actions release validation workflows for OpenClaw development.

How do I automate GitHub Actions release validation for minor code changes?▼

Automating release validation for minor changes uses source code diff analysis to select the cheapest safe test suite and targeted CI lanes, bypassing full repository test execution to streamline production-grade release orchestration.