How do I install the Miniapp Devtools CLI Repair skill?

Run npx skillmds@latest add sun-sunshine06/miniapp-devtools-cli-repair in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Miniapp Devtools CLI Repair safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Miniapp Devtools CLI Repair?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Miniapp Devtools CLI Repair free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Miniapp Devtools CLI Repair?

sun-sunshine06 (@sun-sunshine06) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Miniapp Devtools CLI Repair by sun-sunshine06

Name: Miniapp Devtools CLI Repair
Author: sun-sunshine06

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 b85454b 4 files · 8.9 KB Updated Sep 17, 2026

File contents

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 open to establish IDE connectivity and the live service port.
Use preview as 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 preview over engine build.
Use open first 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 preview is already green or the remaining blocker is a page-side request: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 boundaries
references/example-prompts.md: reusable trigger examples and evaluation notes

---name: miniapp-devtools-cli-repairdescription: 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.---# Miniapp Devtools Cli Repair## OverviewUse 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 Start1. Read `references/cli-repair-playbook.md`.2. Confirm the official DevTools CLI exists and can print help.3. Use `open` to establish IDE connectivity and the live service port.4. Use `preview` as the primary mini program compile check.5. 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 `preview` over `engine build`.- Use `open` first 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 `preview` is already green or the remaining blocker is a page-side `request: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 BoundaryApply 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 fixDo 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 FormatWhen answering, keep the result operational:1. what the CLI exposed2. whether the issue is auto-fixable3. what was changed or what further evidence is still needed4. the next command or user action## Resources- `references/cli-repair-playbook.md`: command ladder, timeout handling, and fix boundaries- `references/example-prompts.md`: reusable trigger examples and evaluation notes

Frequently asked questions