retrospective

To generate a retrospective report, execute the evaluation pipeline script to assess code changes, test coverage, and build status, compiling a structured summary of work completed, quality metrics, and recommended actions.

A coding session retrospective evaluates completed work by analyzing code changes, test coverage, and build status to identify quality issues, surface improvement patterns, and generate actionable recommendations for future development cycles.

Yes, session analysis supports sprint retrospectives and code reviews by executing an evaluation script that assesses code quality metrics and generates structured reports detailing work summaries, observed patterns, and recommended actions.

Automate quality metrics collection by running the retrospective evaluation script, which assesses code changes, test coverage, and build status to produce a structured report with observed patterns and recommended process improvements.

No external dependencies or components are required. The session evaluation runs a standalone script that assesses coding changes and build status to generate a structured retrospective report with quality metrics and recommended actions.

Avoid running a session retrospective when a coding session is incomplete or when build status is failing, as the evaluation relies on assessing completed code changes, test coverage, and stable build results to generate accurate quality metrics.