comprehension-report

Generate an architecture narrative by extracting structured diff data, mapping changes to acceptance criteria, and aggregating decision journal insights into a human-readable PR body. This translates raw code changes into a clear narrative explaining what was built and why.

Map acceptance criteria to implementation evidence by linking concrete diff changes directly to original issue requirements. This structured extraction validates that built features align with requested specifications, enabling automated traceability and stakeholder validation.

Surface architecture decisions and trade-offs in code reviews by aggregating decision journal entries into a structured report. This bridges automated AI outputs and human evaluation by detailing why specific choices were made during implementation.

Create a requirements-adherence report by aggregating decision journal insights and issue context, then mapping them against actual code diffs. This validates traceability and ensures the final implementation aligns with original stakeholder requirements.

Diff analysis extracts implementation details while decision journals provide the reasoning behind choices. Combining them generates a comprehensive PR comprehension report that details both the technical architecture built and the underlying trade-off evaluation.

You need a comprehension report when stakeholders require a clear, human-readable bridge between automated code outputs and business understanding. It is necessary during PR reviews and audits to explain what was built, validate traceability, and transfer architectural knowledge.