
Qiaomu Opencli Autofix
When an opencli adapter breaks because a website changed its DOM or API, this walks you through the repair loop: run the command with OPENCLI_DIAGNOSTIC=1 to get a snapshot, explore the live site with opencli browser to find what moved, patch the adapter source at the exact path it gives you, and retry. It has hard stops for auth and connectivity issues so you don't waste rounds fixing the wrong thing. The 3-retry budget and the "empty doesn't mean broken" section are smart touches. Most useful when you're maintaining adapters for sites that redesign frequently and you'd rather teach Claude to fix them than do it yourself every time.
- skills.sh installs
- 994
- GitHub stars
- 998
- last updated
- Aug 21, 2026
Install
$ npx -y skills add joeseesun/qiaomu-opencli-skills --skill qiaomu-opencli-autofix --agent claude-codeInstalls into .claude/skills of the current project.
Files
OpenCLI AutoFix — Automatic Adapter Self-Repair
When an opencli command fails because a website changed its DOM, API, or response schema, automatically diagnose, fix the adapter, and retry — don't just report the error.
Safety Boundaries
Before starting any repair, check these hard stops:
AUTH_REQUIRED(exit code 77) — STOP. Do not modify code. Tell the user to log into the site in Chrome.BROWSER_CONNECT(exit code 69) — STOP. Do not modify code. Tell the user to runopencli doctor.- CAPTCHA / rate limiting — STOP. Not an adapter issue.
Scope constraint:
- Only modify the file at
RepairContext.adapter.sourcePath— this is the authoritative adapter location (may beclis/<site>/in repo or~/.opencli/clis/<site>/for npm installs) - Never modify
src/,extension/,tests/,package.json, ortsconfig.json
Retry budget: Max 3 repair rounds per failure. If 3 rounds of diagnose → fix → retry don't resolve it, stop and report what was tried.
Prerequisites
opencli doctor # Verify extension + daemon connectivity
When to Use This Skill
Sponsors
Details
- Repository
- github.com/joeseesun/qiaomu-opencli-skills
- Categories
- AI & Agent Building, Debugging
- First seen
- Jun 3, 2026