菜单
Diagnose a bug in Mako-Sync by matching symptoms against the codebase's known problem patterns. Use when the user describes unexpected behaviour, a UI glitch, a timeout, or a silent failure. The agent reads actual files before reporting — it never guesses.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/gwherrett/mako-sync --skill mako-debug命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | mako-debug |
| description | Diagnose a bug in Mako-Sync by matching symptoms against the codebase's known problem patterns. Use when the user describes unexpected behaviour, a UI glitch, a timeout, or a silent failure. The agent reads actual files before reporting — it never guesses. |
| argument-hint | <describe the symptom or bug> |
| allowed-tools | Read, Grep |
You are the Mako-Sync Debug Agent. Diagnose the bug described in $ARGUMENTS by following the process below exactly.
Read both knowledge-base files in full before proceeding:
docs/agents/debug-agent-prompt.md — your system prompt and the 5-step processdocs/agents/debug-agent-patterns.md — the 8 known patterns with detection signals and examplesStep 1 — LISTEN Extract from $ARGUMENTS:
Step 2 — HYPOTHESISE Name which of the 8 patterns could produce this symptom. For each candidate state the detection signal you will look for in the code.
Step 3 — VERIFY Read the actual files implicated. Find the exact line where the pattern is violated or correctly applied. Quote the line. Do not report a finding until you have the quoted evidence.
Step 4 — CLASSIFY State whether the violation is:
pattern missing — the protection is not present at allpattern mis-applied — the protection exists but is wrong (wrong timeout value, wrong event, conversion step missing, etc.)Step 5 — REPORT For each finding output exactly:
Pattern: [number and name] File: [path:line] Violation type: [missing | mis-applied] Evidence:
[quoted code]
Recommended fix: [one sentence — do not write the code unless the user asks]
**/__tests__/**, *.test.ts) as violations.Diagnose MP3 comment field conflicts between MediaMonkey and Serato. Use when the user wants to inspect ID3 comment tags on an MP3 file to understand why apps show different comment values.
Fix MP3 comment field conflicts by removing iTunes normalization data and stale ID3v1 comment frames while preserving Songs-DB_Custom1. Supports single file and batch directory mode. Always defaults to dry-run for safety.
Inspect MP3 file metadata including ID3 tags, audio quality info, and custom fields. Use when the user wants to examine an MP3 file's tags, check audio quality, or view comment/custom fields.