optimizetests

Optimizes OpenClaw test suite performance by refactoring high-latency patterns and inefficient imports.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/wangqianCAI/OBI --skill optimizetests-wangqiancai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: optimizetests
Source: https://github.com/wangqianCAI/OBI/tree/main/.agents/skills/optimizetests
Command: npx skills add https://github.com/wangqianCAI/OBI --skill optimizetests-wangqiancai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses slow CI pipelines and inefficient test execution in OpenClaw projects by identifying performance bottlenecks and optimizing test architecture without compromising coverage.

Core Features & Use Cases

  • Performance Benchmarking: Provides structured commands to measure test wall time, import durations, and resource usage.
  • Optimization Strategies: Guides the refactoring of expensive setups, module resets, and import patterns to improve execution speed.
  • Use Case: When a project's test suite takes too long to run in CI, use this Skill to identify high-latency tests and apply targeted refactoring to reduce total execution time while maintaining full coverage.

Quick Start

Use the optimizetests skill to benchmark the current test suite and identify the slowest import hotspots.

Frequently Asked Questions about optimizetests

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

FAQPage Schema
How do I reduce vitest CI wall time for slow OpenClaw test suites?

To reduce vitest CI wall time, you benchmark test execution to identify high-latency patterns and inefficient module imports. Refactoring expensive setups and import patterns systematically lowers total execution time.

What is the best way to benchmark vitest performance bottlenecks in an OpenClaw project?

Benchmarking vitest performance bottlenecks involves measuring test wall time, import durations, and resource usage using structured commands. This process isolates the slowest import hotspots and expensive setups causing pipeline delays.

How do I refactor inefficient module imports without losing test coverage?

You refactor inefficient module imports while maintaining strict coverage maintenance standards. By applying production-quality code refactoring to expensive setups and resets, test execution speed improves without compromising existing coverage.

Does OpenClaw test optimization work with existing vitest configurations?

OpenClaw test optimization integrates with existing vitest configurations by targeting architectural improvements in test setup. It identifies and refactors high-latency test patterns directly within the current testing framework structure.

When should I optimize test suite performance to avoid CI pipeline delays?

You should optimize test suite performance when a project's test suite takes too long to run in CI. Targeted refactoring of slow import hotspots and expensive setups reduces CI wall time while maintaining full coverage.

Why does my vitest suite have high-latency test patterns and slow imports?

Vitest suites develop high-latency test patterns and slow imports due to inefficient module resets and expensive test setups. Benchmarking resource usage and import durations isolates these specific architectural bottlenecks.