Write it down properly

Everything that outlives the person who wrote it — commit messages, incident reports, and research notes that still mean something in six months.

• Writing Commit Messages — Writes Conventional Commits messages from a staged diff, explaining why a change was made rather than restating what it changed. Use when the user asks for a commit message, mentions committing, or shares a diff and asks how to describe it.
• Writing Postmortems — Turns an incident into a blameless postmortem with a timeline, contributing factors and owned action items, using language that describes systems rather than assigning fault. Use after an outage, a data loss event, a failed deploy, or when the user asks for an incident report or RCA.
• Interviewing Users — Plans and runs customer discovery interviews that surface what people actually did rather than what they say they would do, and turns transcripts into evidence. Use when preparing user research, validating a product idea, writing interview questions, or analysing what customers said.