erne-retrospective

A coding session retrospective evaluates completed work by analyzing changed files, test results, build history, and hook-rule patterns. It identifies improvement opportunities and suggests harness enhancements to refine your development workflow.

Generate a retrospective report after a feature milestone by running the session evaluation script. It analyzes your completed coding session, evaluating changed files, test results, and build history to produce actionable feedback for workflow refinement.

Yes, you need the session evaluation script at .claude/hooks/scripts/evaluate-session.js and access to session logs. These are required to evaluate changed files, test results, build history, and hook-rule patterns for the retrospective report.

Yes, session analysis evaluates test results and build history across planning, coding, testing, and debugging phases. It identifies improvement opportunities and suggests harness enhancements to boost code quality and streamline future builds.

The best way to identify harness enhancements is running a retrospective analysis on hook-rule patterns and build history from your completed session. This evaluation pinpoints specific workflow adjustments to improve code quality.

Automated session evaluation depends on the .claude/hooks/scripts/evaluate-session.js script and accessible session logs. Without these, it cannot evaluate changed files, test results, or build history to generate a retrospective report for improvement suggestions.