qiaomu-opencli-autofix

Diagnose and repair failing OpenCLI adapters with minimal targeted code changes.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/selfagency/agentsy --skill qiaomu-opencli-autofix-selfagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qiaomu-opencli-autofix
Source: https://github.com/selfagency/agentsy/tree/main/.agents/skills/qiaomu-opencli-autofix
Command: npx skills add https://github.com/selfagency/agentsy --skill qiaomu-opencli-autofix-selfagency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically fixes broken OpenCLI adapters when site structure or APIs change, so you can recover from failures without manually debugging adapter code.

Core Features & Use Cases

  • Failure-aware auto-repair loop: Diagnoses the failing adapter via OPENCLI_DIAGNOSTIC, patches the adapter, and retries.
  • Targeted, minimal edits: Modifies only the authoritative adapter file at RepairContext.adapter.sourcePath, avoiding unrelated refactors.
  • Safety hard stops and scoped scope control: Refuses to modify code for authentication, browser connectivity, CAPTCHA/rate limiting scenarios, and enforces a 3-repair-round budget.
  • Root-cause classification by error code: Handles common repairable cases like SELECTOR, EMPTY_RESULT, API_ERROR, TIMEOUT, and PAGE_CHANGED.

Quick Start

Load this skill, run your failing opencli command with OPENCLI_DIAGNOSTIC=1, then have the skill diagnose the error, patch the adapter at the provided sourcePath, and retry up to three rounds.

Frequently Asked Questions about qiaomu-opencli-autofix

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

FAQPage Schema
How do I fix a web scraping adapter when a DOM selector or API endpoint changes?

To fix a web scraping adapter after DOM selector or API endpoint changes, run the failing command with OPENCLI_DIAGNOSTIC=1 to classify the mismatch, patch the adapter source file, and retry up to three rounds.

Why does my OpenCLI adapter return an EMPTY_RESULT or PAGE_CHANGED error?

An EMPTY_RESULT or PAGE_CHANGED error occurs when the target website structure drifts from the adapter's defined selectors or wait conditions, requiring a minimal targeted code patch to the adapter file to restore functionality.

How to diagnose and repair API_ERROR or TIMEOUT failures in OpenCLI adapters?

Diagnose and repair API_ERROR or TIMEOUT failures by running the command with OPENCLI_DIAGNOSTIC=1, applying minimal edits to the adapter sourcePath to correct endpoint or wait condition mismatches, and retrying the original command.

Does the OpenCLI auto-repair process fix AUTH_REQUIRED or BROWSER_CONNECT errors?

The OpenCLI auto-repair process does not fix AUTH_REQUIRED or BROWSER_CONNECT errors because these are hard-stop codes requiring manual intervention for authentication, browser connectivity, or CAPTCHA resolution before retrying.

What is the repair budget limit for retrying failing OpenCLI adapter commands?

The repair budget limit for retrying failing OpenCLI adapter commands is three rounds of diagnose, fix, and retry, ensuring only minimal targeted edits are applied to the authoritative adapter file before stopping.

Can I use OpenCLI adapter repair for web scraping tasks without modifying unrelated code?

You can use OpenCLI adapter repair for web scraping without modifying unrelated code because the process restricts changes exclusively to RepairContext.adapter.sourcePath, preserving adapter output compatibility and avoiding unrelated refactors.