18 lines
1.2 KiB
Markdown
18 lines
1.2 KiB
Markdown
---
|
||
description: Summarize a long file, log, diff, or document into structured notes
|
||
argument-hint: "[file path, log, or topic to summarize]"
|
||
subagent: true
|
||
fork: true
|
||
---
|
||
Summarize: $@
|
||
|
||
Structure your answer as:
|
||
1. **One-paragraph gist** — what this is, in plain terms, at the level a smart non-expert would understand
|
||
2. **Key points** — 5 to 10 bullets, ordered by importance, each ≤2 lines
|
||
3. **Structure** — how the content is organized: sections, layers, time periods, components
|
||
4. **Important details** — names, numbers, paths, error codes, dates, anything concrete that a later reader will need verbatim
|
||
5. **What's missing or unclear** — gaps, assumptions, things that need a follow-up read
|
||
6. **Pointer to deep-dive sections** — if a reader only has 5 minutes, which 2–3 sections cover 80% of the value
|
||
|
||
Be ruthless about compression. If the source is long, the summary should be short — that's the whole point. Prefer concrete over abstract. Quote exact strings (paths, error messages, identifiers) rather than paraphrasing them, because the reader will likely need to grep for them later. Do not editorialize or add recommendations; just compress.
|