wrapup

Save session context, log mistakes, and extract lessons to documentation files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/petrogurcak/skills --skill wrapup-petrogurcak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrapup
Source: https://github.com/petrogurcak/skills/tree/main/plugins/development/skills/wrapup
Command: npx skills add https://github.com/petrogurcak/skills --skill wrapup-petrogurcak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the crucial end-of-session reflection process, ensuring that valuable context, lessons learned, and identified mistakes are systematically captured and saved.

Core Features & Use Cases

  • Context Saving: Automatically updates ACTIVE_CONTEXT.md with session outcomes.
  • Mistake Logging: Identifies and logs errors or unexpected behaviors in mistakes.md.
  • Lessons Learned: Extracts and proposes new knowledge or useful workarounds.
  • Documentation Review: Checks for necessary updates to project documentation.
  • Use Case: After completing a complex development task and merging the code, use this Skill to ensure all relevant information about the session is preserved for future reference and team knowledge sharing.

Quick Start

Use the wrapup skill to perform end-of-session reflection and save context.

Frequently Asked Questions about wrapup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save session context and document lessons learned after a development session?

To save session context and document lessons learned, perform an end-of-session reflection that updates ACTIVE_CONTEXT.md, logs mistakes in mistakes.md, and identifies necessary documentation updates to preserve project knowledge.

What is the best way to log development mistakes and extract lessons learned automatically?

Logging development mistakes and extracting lessons learned is best handled by an automated reflection process that identifies errors, saves them to mistakes.md, and proposes new knowledge or workarounds for future reference.

When should I run an end-of-session reflection and context saving process?

You should run an end-of-session reflection and context saving process after merging to development, when ending a coding session, or when triggering a wrapup command to ensure all context is captured.

Can I use session wrapup tools to check for necessary project documentation updates?

Yes, session wrapup tools can check for necessary project documentation updates by reviewing the completed development work and identifying which docs require modifications to stay current with the codebase.

Does end-of-session reflection work without manual context saving and mistake logging?

End-of-session reflection requires proactive checks for context saving and mistake logging to function correctly, ensuring ACTIVE_CONTEXT.md and mistakes.md are systematically updated without manual intervention.

What are the limitations of relying on automated session wrapup for knowledge management?

The limitation of automated session wrapup is that it strictly depends on triggering events like merge actions or specific commands, meaning unmerged or untriggered session work might not have its context saved.