opencli-autofix

Diagnoses and repairs broken OpenCLI adapters after command failures.

28.0k|2.8k|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jackwener/OpenCLI --skill opencli-autofix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencli-autofix
Source: https://github.com/jackwener/OpenCLI/tree/main/skills/opencli-autofix
Command: npx skills add https://github.com/jackwener/OpenCLI --skill opencli-autofix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically diagnose and patch failed OpenCLI adapters when a site changes its DOM, API, or response schema, then retry and document upstream fixes.

Core Features & Use Cases

  • Automatic adapter diagnosis, patching, and retry workflow when an opencli command fails.
  • Guided repair process with safety boundaries and a GitHub issue draft for upstream fixes.
  • Works with any AI agent and supports per-site adapter repair orchestration.

Quick Start

Invoke an opencli command that fails to trigger the autofix workflow to diagnose, patch, and retry the adapter.

Frequently Asked Questions about opencli-autofix

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

FAQPage Schema
How do I automatically diagnose and repair broken CLI adapters when a website changes its DOM or API?

To automatically repair broken CLI adapters, this Skill diagnoses command failures caused by DOM, API, or response schema changes, applies minimal patches to the adapter source, and retries the command within a strict three-round repair budget.

What is the process for patching failed OpenCLI adapters after an upstream schema update?

Patching failed OpenCLI adapters involves diagnosing the command failure, applying minimal edits restricted to the adapter source path to preserve output structure, retrying the command, and drafting a GitHub issue to document the upstream fix.

Can I use automated adapter repair workflows with any AI agent?

Yes, automated adapter repair workflows work with any AI agent, guiding the orchestration of diagnostics, patching, and retrying for per-site adapter repairs without requiring specific agent dependencies.

What are the safety boundaries and limitations when applying automated CLI adapter patches?

Safety boundaries for automated CLI adapter patches restrict edits to the adapter source path, enforce minimal changes to preserve output structure, and limit the repair process to a maximum of three rounds to prevent excessive modifications.

Why does my opencli command fail after a site updates its response schema, and how do I fix it?

An opencli command fails because site response schema changes break the adapter, and you fix it by triggering the autofix workflow to diagnose the mismatch, patch the adapter, and retry execution.