postmortem

To analyze conversation transcripts for anti-patterns, you can use predefined detection heuristics to scan Worker, Reviewer, and Orchestrator logs. This identifies structural problems and protocol deviations, generating a structured postmortem report with actionable recommendations.

Automating issue tracking from debugging transcripts involves scanning logs for critical and warning issues, then proposing GitHub issues based on those findings. The system requires user approval before creating these tickets, streamlining the debugging process.

Yes, transcript analysis can scan Orchestrator and Worker logs to find protocol deviations. It uses predefined detection patterns to identify communication breakdowns and structural problems, outputting a clear postmortem report.

To generate a postmortem report for a specific issue number, run the analysis command on that issue. The system scans the relevant conversation transcripts to identify inefficient steps and compiles the findings into a structured report.

Yes, you need predefined detection pattern heuristics to run a transcript postmortem analysis. These heuristics are required to detect structural problems, protocol violations, and anti-patterns within the conversation transcripts.

You should run a postmortem analysis after a complex development cycle to quickly identify any communication breakdowns, protocol violations, or inefficient steps that occurred, and generate tickets to address them.