opencli-autofix

Analyze trace artifacts, patch OpenCLI adapter source code, retry commands, and file GitHub issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automatically fixes broken OpenCLI adapters when commands fail, guiding through collecting trace artifacts, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix.

Core Features & Use Cases

  • Adapter Self-Repair: Automatically diagnose and fix OpenCLI adapter issues like DOM changes, API changes, or runtime errors.
  • Trace Analysis: Collects and analyzes trace artifacts to determine the root cause of adapter failures.
  • Patch Execution: Applies targeted fixes to the adapter source code based on the analysis.
  • Retry Mechanism: Retries the command after fixing the adapter, up to 3 rounds.
  • Upstream Issue Reporting: Files a GitHub issue with the fix for the adapter when the local repair is successful.

Quick Start

Run the failing opencli command and follow the guided steps provided by the skill to repair 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 repair broken OpenCLI adapters when commands fail?

To repair broken OpenCLI adapters, run the failing command and follow the guided steps to collect trace artifacts, apply source code patches, and retry execution. The skill automatically diagnoses issues like DOM or API changes and attempts up to 3 retry rounds.

What causes OpenCLI adapter failures that require trace analysis?

OpenCLI adapter failures are typically caused by DOM changes, API changes, or runtime errors in the adapter source code. Trace analysis collects and examines artifacts from the failed command execution to determine the exact root cause of these issues.

Do I need access to adapter source code to fix OpenCLI runtime errors?

Yes, you need access to the adapter source code to fix OpenCLI runtime errors. The skill applies targeted patches directly to the adapter source code based on trace artifact analysis, then verifies the fix by retrying the command.

Can I automatically file upstream GitHub issues after fixing an OpenCLI adapter?

Yes, you can automatically file upstream GitHub issues after fixing an OpenCLI adapter. Once a local repair is successfully verified through command retries, the skill files a GitHub issue containing the applied fix for upstream resolution.

What happens if the OpenCLI adapter repair fails after multiple retries?

The retry mechanism attempts to fix the OpenCLI adapter and retry the command for up to 3 rounds. If the repair remains unsuccessful after these attempts, the automated patching cycle stops to prevent infinite loops.

What is the best way to diagnose OpenCLI adapter issues from failed command traces?

The best way to diagnose OpenCLI adapter issues is by collecting and analyzing trace artifacts from the failed command. This trace analysis identifies whether the failure stems from DOM changes, API changes, or runtime errors before applying targeted fixes.