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.
소스 정보
- 저장소
- leolionart/media-library-manager
- 최근 소스 활동
- 2026년 4월 5일 09:59
- 감지된 SKILL.md 언어
- 영어
- 스타
- 1
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- 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"
GitHub에서 보기