Summarize an engineering change with evidence | DevPrompt Lab

Explain what changed, why, how it was verified, and what remains uncertain.

workflow · Delivery · beginner

English Tiếng Việt

A handoff workflow for reporting implementation results clearly without overstating validation or scope.

Reusable content

Summarize the completed engineering change for a teammate. State the user-visible change, important implementation decisions, affected files or systems, and compatibility impact. List checks actually run with pass or fail results. Call out tests that were not run and why, plus relevant limits or follow-up work. Do not claim completion for work that remains. Use concrete wording and link to the primary files.

Changes: {{CHANGES}}

Reason: {{WHY}}

Validation: {{VALIDATION}}

Limitations: {{LIMITATIONS}}

How to use it

Base the summary on the final diff and captured command results, not the original plan.

Example

Added owner-scoped project APIs and deterministic generator functions. TypeScript lint and PHP syntax checks passed; database migration tests remain unrun because no isolated test database was available.