session-wrap

Automate coding session wrap-up by running parallel multi-agent analysis to inspect git status and changed files, summarizing work, extracting learnings, and proposing follow-up actions. This structured workflow ensures valuable insights and documentation updates are captured at session end.

Generating documentation updates and prioritized follow-up tasks after a feature implementation is best handled by multi-agent analysis of your coding session. The process extracts TIL-style summaries and suggests automation opportunities before interactively executing selected changes.

Multi-agent analysis detects duplicate proposals using a sequential validation phase that checks generated documentation updates and tasks for duplicates, merging or skipping proposals before any changes are applied to ensure clean, actionable results.

Yes, automated session analysis integrates results and interactively asks which actions to take, executing selected actions such as committing git changes or creating documentation updates directly. This ensures you maintain control over applied modifications.

No dependencies are required to run multi-agent coding session analysis. The skill operates independently to inspect git status, analyze changed files, and generate prioritized task lists without needing external packages or additional environment setup.

You should avoid using automated session wrap-up when your coding session lacks meaningful git changes or file modifications to analyze. Without updated files or decisions to inspect, the multi-agent analysis cannot generate useful documentation updates or follow-up tasks.