Read Logs Usage

How to respond

• If the user invoked this skill without a concrete task, explain what the plugin does and when to reach for /read-logs.
• If they need setup, point them at this plugin's README.md (the canonical setup home) — VS Code/Cursor dapLogFile, or the Zed/script task.
• If they already have a concrete log-reading task, briefly explain the fit and then run /read-logs.
• Do not reply with filler like "skill loaded" or "ready for the task" before explaining the plugin.

What this plugin does

• Lets Claude read the running app's latest flutter run output as on-demand context, via /read-logs <task> — instead of pasting terminal logs.
• Captures flutter run output per-project to /tmp/flutter-<repo>.log (worktree-stable via --git-common-dir, overwritten each launch). Two formats, auto-detected: Zed script transcript and VS Code/Cursor dapLogFile (DAP).
• Reads task-led — reads the whole short run, or investigates a long one against your question (errors, event ordering, a feature, …) — flags stale runs, and on first use guides editor setup.

When to use it