optimizetests

Identify and speed up slow OpenClaw tests by reducing import overhead and misplaced coverage.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rigeoben/fairy --skill optimizetests-rigeoben
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: optimizetests
Source: https://github.com/rigeoben/fairy/tree/main/.agents/skills/optimizetests
Command: npx skills add https://github.com/rigeoben/fairy --skill optimizetests-rigeoben

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline OpenClaw test suites by reducing runtime, minimizing import overhead, and relocating misplaced coverage without sacrificing test quality.

Core Features & Use Cases

  • Benchmark-driven identification of slow tests and hotspots.
  • Guided workflow to optimize imports, setup, and coverage placement.
  • CI-friendly, reproducible improvements with clear runbooks and commit traces.

Quick Start

Run the optimizer against your OpenClaw repository following the Runbook to measure impact and apply changes.

Frequently Asked Questions about optimizetests

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

FAQPage Schema
How do I speed up slow OpenClaw tests without losing coverage?

Benchmarking identifies slow OpenClaw tests by measuring runtime hotspots deterministically. This process tracks import overhead and coverage placement without changing test logic, ensuring reproducible results for optimization.

How do I optimize OpenClaw CI pipelines for test performance?

You can optimize OpenClaw CI pipelines by applying tooling adjustments and guided runbooks. This method targets import overhead and setup inefficiencies to produce reproducible, CI-friendly runtime improvements with commit traces.

What causes high import overhead in OpenClaw test suites?

High import overhead in OpenClaw test suites stems from misplaced setup and coverage workflows. Benchmarking identifies these hotspots so you can apply tooling adjustments that reduce runtime without adding shards.

Do I need to change test logic to reduce OpenClaw test runtime?

No, you do not need to change test logic to reduce OpenClaw test runtime. Optimization relies on deterministic benchmarking, runbooks, and tooling adjustments to improve performance while preserving test coverage.

What is the best way to benchmark OpenClaw test hotspots?

The best way to benchmark OpenClaw test hotspots is using deterministic measurement to track runtime, imports, and coverage workflows. This identifies slow tests and guides CI-friendly optimizations with clear commit traces.