mini-program-debugging-skill SKILL.md skillA
mini-program-debugging-skill from nocodemrli/mini-program-engineering-skill-suite is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nocodemrli/mini-program-engineering-skill-suite/mini-program-debugging-skill@git:20261011.4bc5561Pins git:20261011.4bc5561 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nocodemrli/mini-program-engineering-skill-suite
- Path
skills/mini-program-debugging-skill/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261011.4bc5561, committed Oct 11, 2026
- First version recorded
- Aug 13, 2026
- Size
- 5,456 bytes
- Repository stars
- 95
- License
- MIT
Diagnose and fix mini-program failures through reproducible, evidence-driven root-cause analysis across source, state, asynchronous timing, caches, mock data, build versions, platform behavior, devices, cloud calls, and external services. Use when users report white screens, crashes, stale or jumping values, missing data, intermittent behavior, permission failures, performance stalls, device-only defects, API or cloud-function errors, source-versus-build mismatches, or regressions whose cause…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# /mini-program-debugging-skill — 小程序问题调试 从可重复症状建立证据链，定位能解释关键现象的根因，再以失败复现、最小修复和回归测试闭环。诊断请求本身不授权修改；用户要求修复或任务明确包含修复时，才进入受控改动。 ## 输入与观察基线 - 接收症状、截图/视频、日志、错误码、复现步骤、项目事实图或失败测试。 - 先固定源码/构建版本、分支/文件状态、运行环境、设备/工具、账号/数据状态、网络与时间，再写最小复现和预期/实际差异。 - 截图是现象证据，不是根因；历史日志不能证明当前构建仍有同一问题。 - 若只有产品语义争议而非故障，退回产品规格；若根因已证实且只需实施，可交给实现阶段。 ## 证据驱动调试流程 1. 用最少步骤稳定复现；无法稳定复现时记录频率、前置状态、成功/失败样本和最后正常版本。 2. 建立时间线与证据链：输入、默认值、状态迁移、异步时序、缓存、模拟数据、接口、渲染、构建版本、设备/平台结果。 3. 提出至少两个可证伪的竞争假设，为每个假设记录支持/反对证据和最小判别实验；先执行信息增益最高的只读检查。 4. 外部服务失败按调用前、传输、服务返回、业务有效性校验、持久化/扣减和界面反馈分段，核对错误码、参数、耗时、重试与幂等，敏感值只报告存在性；只有有效结果允许改变完成态或扣次数/费用。 5. 根因结论必须解释主要现象和边界样本；证据不足时保持“最可能假设”，不把相关性写成根因。 6. 修复前写能失败的回归测试或自动复现；做最小修复后验证原症状、同类状态、共享契约和反例，避免只修截图实例。 7. 工具异常、超时、用户中止或外部响应不明确时，按 [中断恢复协议](references/interruption-recovery-protocol.md) 将在途动作记为 `unknown`，刷新事实后再决定是否重试。 用户禁止启动业务或构建进程时，读取既有日志、产物、工作区和进程元数据的只读检查命令不属于启动业务或构建进程；除非用户明确禁止一切工具读取，否则先执行这些检查，不以“需要授权检查”代替事实刷新。 已有产物可读时，计算并输出已有产物指纹（优先 SHA-256）并绑定路径；工具失败时输出失败原因和未取得指纹，不能只写“已检查产物”。 8. 使用 [问题调试工作流](references/debugging-workflow.md) 自检，并按 [调试报告模板](assets/debugging-report.md) 输出证据、修复与剩余风险。 ## 禁止性策略 - 不用延长等待、吞掉错误、硬编码成功、强制刷新或清空缓存掩盖明确失败。 - 不把日志减少、占位内容、视觉遮挡或重试次数增加当成根因修复。 - 不在没有版本/产物证据时把源码修改当成设备问题已修复。 …
Read the whole file at its exact version.
How to install
mdr add nocodemrli/mini-program-engineering-skill-suite/mini-program-debugging-skill@sha256:afde091e316fe29bThe line at the top of this page pins the label git:20261011.4bc5561, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6tbnroa6fgyeomfp)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 13, 2026 and Oct 11, 2026, about one every 29 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.4bc5561 latest | 2026-10-11 | 4bc5561 | 5,456 B | A | view · diff |
| git:20260928.e9e955a | 2026-09-28 | e9e955a | 5,215 B | A | view · diff |
| git:20260813.cfc2393 | 2026-08-13 | cfc2393 | 5,005 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5456 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nocodemrli/mini-program-engineering-skill-suite · 95 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6tbnroa6fgyeomfp GET https://markdownregistry.com/api/v1/resolve?ref=nocodemrli/mini-program-engineering-skill-suite/mini-program-debugging-skill GET https://markdownregistry.com/api/v1/blob/afde091e316fe29b1852dc196136a82b097a3f4b90bc41c587d961f4f473f7f5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from nocodemrli/mini-program-engineering-skill-suite
Every file in nocodemrli/mini-program-engineering-skill-suite