What was wrong
A plain-language explanation of the failure and why it appeared.
After the repair
The next developer should know what changed and why.
A quick patch may stop the immediate error, but it should not leave the application even harder to understand. A useful repair gives the team a working result and a clear picture of what was done.
What changed
The files, settings, packages, or services that were adjusted—without burying the explanation in jargon.
What was checked
The important pages and user actions that were tested after the repair.
What still needs attention
Known risks, future cleanup, and any work that was intentionally left outside the rescue.
The goal is not only to make the application run today. It is to leave your team in a better position for the next change.
Talk about your application