メニュー
View application logs via the project's bash script. Use when debugging issues, investigating errors, or when the user asks to check or show logs. Logs are the primary way to see what the app is doing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Triage a WhisperShortcut chat-window main-thread freeze from the watchdog's on-disk hang captures and app logs — classify real vs. false-positive, localize the wedge, confirm whether the shipped fix held, and continue root-causing new variants. Use when the app beachballs/freezes/pins CPU during chat, when a new hang-*.txt appears, or when asked to investigate a chat hang.
Build, launch, drive, screenshot, and walk through the WhisperShortcut macOS menu-bar app from a user's perspective. Use when asked to run, start, launch, build, screenshot, test onboarding, cognitive walkthrough, first-run activation, or visually confirm UI changes in the real app (not just tests). Covers Welcome onboarding, status menu, Settings, and Chat.
Mine the local user-interaction JSONL logs for systematic failures and propose improvements across system prompts, defaults, code logic, logging, and UI. Use when the user asks for improvements based on actual usage — e.g. "what's going wrong in Dictate Prompt?", "analyze my recent interactions", "find patterns in the logs", "what should we improve based on how I'm using the app?".
Validate end-to-end that Smart Improvement audio verification is actually working — audio is captured for dictation, selected content-aware to verify recurring candidate terms, attached only when the asymmetry rule passes, used by the dictation and Whisper Glossary focuses, and retained across runs (pruned by age). Use when the user asks "is audio verification working?", after implementing or modifying the Smart Improvement audio verification feature, or when investigating why a glossary/dictation suggestion was or was not produced.
Systematically reviews all LLM-context files in this repo (.cursor/commands/, .cursor/rules/, .cursor/skills/) for stale references, factual drift vs the current codebase, redundancy across files, and files that no longer earn their slot. Produces a tiered report (broken / drift / dedup / hygiene). Use when the user asks to audit, review, check, or validate LLM-context files, cursor rules, claude skills, prompt files, or "are these instructions still correct".
Look up current official documentation AND current model lineups for OpenAI, Google Gemini, and xAI (Grok). Use BEFORE adding/changing model IDs, before answering model-capability questions (e.g. "does gpt-4o-transcribe accept a system prompt?"), AND proactively whenever you touch chat/transcription/TTS code paths (provider files, SettingsConfiguration, TranscriptionModels, ChatModelCommandResolver, SpeechService) — compare our current defaults to what each provider has shipped recently, and surface upgrade suggestions to the user if newer GA models exist. AI moves fast — always check live docs first.
| name | view-logs-via-bash |
| description | View application logs via the project's bash script. Use when debugging issues, investigating errors, or when the user asks to check or show logs. Logs are the primary way to see what the app is doing. |
Logs are the primary debugging surface. View them via the project script (per the always-applied rule in .cursor/rules/index.mdc) — not via direct file access.
bash scripts/logs.sh [options]
| Purpose | Command |
|---|---|
| Last time window (e.g. 2 min) | bash scripts/logs.sh -t 2m |
| Live stream of all logs | bash scripts/logs.sh |
| Filter by text | bash scripts/logs.sh -f 'PROMPT-MODE' or -f 'Error' |
| Last hour | bash scripts/logs.sh -t 1h |
When debugging, check logs first (-t 5m / -t 2m) and use -f to filter by mode or errors (PROMPT-MODE, Speech-to-Text, Error).
logs.sh reads the macOS unified-logging buffer (log show/log stream). That buffer rolls over after a while, so for older sessions widen the window (-t 24h / -t 48h) and don't assume "no output" means it never happened.DebugLogger call, but the app also keeps a structured user-interaction log (interactions-YYYY-MM-DD.jsonl under the canonical data dir, see index.mdc → Data Directories). That JSONL records the user message + final model response per interaction, but not individual chat tool calls — for the tool-call trail (e.g. AI Chat → Google Calendar), grep the unified log for CHAT-TOOL-CALL / CHAT-TOOL-RESULT / GOOGLE-CALENDAR.