Dev Experience Summarizer

The Problem

Key debugging conclusions often remain scattered across chat threads, stack traces, temporary fixes, and refactoring notes. Engineers may remember the fix but later struggle to reconstruct the root cause, and teams cannot reuse the lesson. Pasting raw conversation into a doc can also add conversational noise and expose sensitive details such as IPs, tokens, absolute paths, or production data.

How It Works

The skill converts fragmented dev context into a shareable technical note using a fixed workflow:

• Context extraction: identifies the core issue, error signals, failed attempts, final fix, and key before / after code changes.
• Mandatory desensitization: applies desensitization-rules.md before rendering, replacing IPs, tokens, real business data, and absolute paths.
• Template-driven output: uses summary-template.md to organize background, root cause, solution, and reusable takeaways.
• Markdown delivery: can preview the note first or save it to a target file such as experience.md.

Boundaries

It fits bug postmortems, refactoring summaries, incident notes, and team knowledge capture. It does not replace formal incident reports, audit logs, or compliance documentation. When code or context may contain secrets, the safe default is to desensitize rather than preserve raw details.