miniapp-devtools-cli-repair
Diagnose WeChat DevTools failures through the official CLI instead of relying only on GUI screenshots. Use when Codex needs to run `open`, `preview`, or related commands, discover the live service port, classify whether a failure is CLI-visible, host-side, or outside preview scope, and apply or suggest only safe repo-level fixes.
Sun-sunshine06 · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Sun-sunshine06/miniprogram-skills --skill miniapp-devtools-cli-repair技能说明
name: miniapp-devtools-cli-repair
description: Diagnose WeChat DevTools failures through the official CLI instead of relying only on GUI screenshots. Use when Codex needs to run open, preview, or related commands, discover the live service port, classify whether a failure is CLI-visible, host-side, or outside preview scope, and apply or suggest only safe repo-level fixes.
tools:
- Bash
- Read
- Edit
- Glob
- Grep slash_command: /miniapp-devtools-cli-repair
Miniapp Devtools Cli Repair
Overview
Use this skill when the user needs CLI-visible evidence from WeChat DevTools. Treat the official CLI as the primary observability surface for compile and preview failures.
Quick Start
- Read
references/cli-repair-playbook.md. - Confirm the official DevTools CLI exists and can print help.
- Use
opento establish IDE connectivity and the live service port. - Use
previewas the primary mini program compile check. - Classify the result as:
- CLI-visible and auto-fixable
- CLI-visible but not safe to auto-fix
- host or account blocker
- outside preview scope and better handled by GUI or service-level debugging
Core Rules
- Prefer the official WeChat DevTools CLI over screenshots for first-pass diagnosis.
- Treat CLI output, exit code, process state, and local logs as primary evidence.
- For miniapp compile diagnosis, prefer
previewoverengine build. - Use
openfirst when the live service port is unknown or the current IDE session is suspect. - Auto-fix only repository-scoped problems such as root-path drift, page-path mismatch, or small syntax issues surfaced with exact locations.
- If
previewis already green or the remaining blocker is a page-siderequest:fail, do not keep grinding CLI repair; move to GUI/runtime or service debugging. - Do not claim full coverage when the error exists only in GUI-only panels, runtime requests, or compile-mode menus.
Auto-Fix Boundary
Apply fixes automatically only when they are coherent and local to the repo:
- repair
project.config.json - repair
tsconfig.json - repair
app.json - delete wrong-root residue
- restore tracked files
- replace a pinpointed unsupported syntax form with an equivalent narrow fix
Do not auto-fix without explicit user direction when the change would alter app strategy, publish state, backend settings, or broad syntax across the repo.
Output Format
When answering, keep the result operational:
- what the CLI exposed
- whether the issue is auto-fixable
- what was changed or what further evidence is still needed
- the next command or user action
Resources
references/cli-repair-playbook.md: command ladder, timeout handling, and fix boundariesreferences/example-prompts.md: reusable trigger examples and evaluation notes