メニュー
Check music production infrastructure. Auto-run when: operator mentions MIDI, audio, music production, beats, or studio setup, when audio/MIDI errors appear in tool output (PostToolUse suggests it), or user asks about studio. Invoke proactively without asking.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Background CI monitor for a PR. Auto-run when: PostToolUse detects a PR was just created (suggests it with PR number), user asks to watch CI, or after pushing to a branch with an open PR. Takes PR number as argument. Invoke proactively without asking.
Run the health monitor and report results. Auto-run when: session-context shows health is degraded or failed, after infrastructure changes (docker, systemd), when a service appears unreachable, or user asks about system health. Invoke proactively without asking.
Audit installed flatpak apps and find native alternatives. Auto-run when: storage-audit reveals large flatpak usage, operator mentions app performance issues related to sandboxing, or user asks about flatpaks. Invoke proactively without asking.
Audit branches across all repos and clean up. Auto-run when: session-context reports >3 non-main branches across repos, no-stale-branches hook blocks a branch create, after merging PRs, or user asks about branch cleanup. Invoke proactively without asking.
Scan for and resolve merge conflict markers. Auto-run when: conflict-marker-scan PostToolUse hook fires a warning, git merge/rebase/cherry-pick output shows CONFLICT (PostToolUse suggests it), or user asks to fix conflicts. Invoke proactively without asking.
Trace consent provenance. Auto-run when: work touches files containing personal data (profiles/, agents processing person names), after adding new data sources or storage, or user asks about consent or data protection. Invoke proactively without asking.
| name | studio |
| description | Check music production infrastructure. Auto-run when: operator mentions MIDI, audio, music production, beats, or studio setup, when audio/MIDI errors appear in tool output (PostToolUse suggests it), or user asks about studio. Invoke proactively without asking. |
Check music production infrastructure:
aconnect -l 2>/dev/null
aplay -l 2>/dev/null
lsmod | grep -i virmidi
docker ps --filter "name=midi" --format "table {{.Names}}\t{{.Status}}" 2>/dev/null
Report MIDI port connections, audio device availability, virtual MIDI status, and any MIDI Docker containers. Summarize what is connected and what is missing.