runtime-diagnostics
Debug the local media-library-manager runtime by inspecting jobs, ports, reports, state artifacts, and backend health. Use when the dashboard looks stale, API behavior differs from edited files, a job is stuck, a scan keeps timing out, or the backend needs a clean restart.
Datos de origen
- Repositorio
- leolionart/media-library-manager
- Última actividad en el origen
- 5 de abril de 2026 a las 09:59
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 1
- Forks
- 0
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Explorador de archivos
2 archivosMostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- runtime-diagnostics
- description
- Debug the local media-library-manager runtime by inspecting jobs, ports, reports, state artifacts, and backend health. Use when the dashboard looks stale, API behavior differs from edited files, a job is stuck, a scan keeps timing out, or the backend needs a clean restart.
# Runtime Diagnostics
Use this skill to understand what the running app is actually doing before changing code or blaming the UI.
## Workflow
1. Inspect runtime state first.
Read `/api/process` and `/api/state`.
Compare live state with files under `data/`.
2. Check ports and processes.
In this repo, Vite commonly runs on `127.0.0.1:5173` and the Python backend on `127.0.0.1:8766`.
Confirm which process is actually serving the current API.
3. Inspect logs and artifacts.
Check `current_job.logs`, `activity_log`, and relevant saved artifacts such as `last-path-repair-scan.json`.
4. Restart cleanly when needed.
Stop the Python backend, confirm the port is free, then restart with the repo's `PYTHONPATH=src` setup and the correct `data/app-state.json`.
5. Re-verify after restart.
Confirm that the live API reflects the edited code and current state file before resuming workflow operations.
## Guardrails
- Distinguish between stale saved reports and live provider reality.
- Do not assume Vite and the Python backend restarted together.
- Prefer direct API checks over guessing from the UI.
## Typical Requests
- "Kiểm tra backend đang chạy code nào"
- "Tại sao UI và file state không khớp"
- "Restart backend sạch rồi verify lại"
Ver en GitHub