| name | performance-pr-snapshot |
| description | Use when the winning optimization is chosen and you need a crisp PR-ready snapshot: problem, evidence, benchmark table, code change summary, risk notes, and the exact story to tell in a demo. |
Performance PR Snapshot
Package the win so another person can merge it, review it, or demo it in under a minute.
This skill turns the work into a compact narrative with numbers. Optimize for clarity, credibility, and reuse in a PR body, Slack update, or live demo.
Deliverables
- Problem statement
- Baseline and winning benchmark numbers
- Change summary
- Risk and follow-up notes
- A compact PR or demo narrative
Workflow
- Collect the facts.
Pull the target endpoint, the baseline trace summary, the winning benchmark numbers, and the files changed.
- Write the story in order.
Start with what was slow, then what changed, then what improved.
- Include a benchmark table.
Keep it small and readable. Before and after is usually enough unless the evaluator compared multiple candidates.
- State the risk honestly.
Note any missing test coverage, cache invalidation risk, edge-case uncertainty, or follow-up work.
- End with the demo line.
Summarize the visible win in one sentence someone can say out loud.
Suggested Sections
- Summary
- Baseline
- Winning change
- Benchmark results
- Risk and follow-up
Guardrails
- Do not bury the performance number.
- Do not over-explain the implementation.
- Keep the snapshot usable as a PR body with minimal editing.
- Prefer measured language over hype unless the data clearly supports the claim.
