summarization-rules-evidence-first_skill

Overview

This skill provides evidence-first summarization rules that present data and metrics before conclusions to boost credibility and reduce token use. It gives concrete templates, formatting guidance, and examples for bug reports, incidents, performance issues, and status updates. The result is shorter, verifiable, and more actionable summaries.

How this skill works

The skill inspects narrative content and restructures it to lead with precise evidence: metrics, timestamps, file locations, and counts. It replaces vague adjectives with numbers, swaps general statements for specific items, and applies templates that favor lists, tables, and code references. Outputs are optimized for brevity, clarity, and verifiability.

When to use it

• Incident reports that require rapid triage and clear root-cause evidence
• Bug reports where exact error messages, frequency, and location matter
• Performance summaries and postmortems needing metrics and before/after comparisons
• Status updates for teams and stakeholders who need concise progress indicators
• Code reviews with specific file:line issues and actionable recommendations

Best practices

• Always start with evidence: metric, timestamp, count, or error string
• Prefer numbers over adjectives (e.g., '2.5s' not 'very slow')
• Be specific: include file:line, exact message, and affected scope
• Use lists or tables for multiple items and code blocks for exact snippets
• Keep action items precise and tied to expected metric improvements

Example use cases

• Turn a long outage narrative into a compact incident summary with impact, root cause, fix, and prevention steps
• Convert vague performance notes into a metrics-first brief showing before/after and recommended fixes
• Generate a bug report template populated with error, frequency, affected users, and exact location
• Produce sprint status bullets that show completed work, blocked items, and percent complete
• Create code review notes listing added/modified/removed files and file:line issues