session-retrospective

You can automate GitHub issue creation for session improvements by triggering a retrospective that reviews conversations and batch-registers structured issues. It captures auth, tooling, docs, and workflow gaps using a Background, Problem, Proposal, and Context format, with a dry-run option for safe validation.

A session retrospective is an automated review process that surfaces actionable improvement points from recent conversational interactions across engineering and product teams. It categorizes findings into auth, conventions, tooling, docs, workflow, and error handling to generate concrete GitHub issues.

Yes, you can preview GitHub issues before batch-creating them by using the built-in dry-run mode. This allows you to validate the structured Background, Problem, Proposal, and Context formats for each improvement point before actually posting them to your repository.

Yes, the session retrospective skill supports both batch and selective issue creation. You can choose specific improvement points from the session review to register as structured GitHub Issues, rather than automatically posting all surfaced gaps across auth, tooling, docs, and workflow categories.

An automated session retrospective covers common engineering categories including auth, conventions, tooling, docs, workflow, and error handling. It scans conversations to surface concrete improvement points within these domains, generating structured GitHub issues for engineering and product teams.