wrap-up

Execute a four-phase end-of-session wrap-up with Korean Conventional Commits.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Palbahngmiyine/harness --skill wrap-up-palbahngmiyine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap-up
Source: https://github.com/Palbahngmiyine/harness/tree/main/skills/wrap-up
Command: npx skills add https://github.com/Palbahngmiyine/harness --skill wrap-up-palbahngmiyine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides and automates a structured end-of-session wrap-up, consolidating actions, memory, and learnings into a single report.

Core Features & Use Cases

  • Phase-based workflow across four phases: Ship It, Remember It, Review & Apply, and Publish It, producing a consolidated summary and ensuring follow-ups.
  • Memory and governance: prompts for capturing insights into memory and enforcing Korean Conventional Commits for traceable changes.
  • Report generation and handoff: creates a shareable end-of-session report and ensures files are organized per project conventions.

Quick Start

Run the wrap-up to execute the four-phase end-of-session process and generate a final report.

Frequently Asked Questions about wrap-up

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

FAQPage Schema
How do I automate an end-of-session wrap-up for software development?

A structured end-of-session wrap-up consolidates development actions, captured memory, and project learnings into a single report. It guides memory capture, enforces Korean Conventional Commits for traceable changes, and generates a shareable summary to ensure follow-ups.

How does conventional commits enforcement work during session shutdown?

Conventional commits enforcement during session shutdown works by applying Korean Conventional Commits standards to code changes. This ensures traceable modifications across the four-phase workflow, linking the final session report directly to the structured commit history.

What's the best way to consolidate project memory and learnings before closing a session?

The best way to consolidate project memory is through a phase-based workflow that prompts you to capture insights and apply learnings. It organizes files per project conventions and generates a shareable report to ensure all session memory and follow-ups are documented.

Can I use this wrap-up workflow for code reviews and project retrospectives?

Yes, this wrap-up workflow applies to code reviews and project retrospectives. It coordinates a structured shutdown across four phases to consolidate development actions, capture memory, and generate a final report for any software development session.

What phases are included in a structured session shutdown?

A structured session shutdown includes four phases: Ship It, Remember It, Review & Apply, and Publish It. These phases execute sequentially to consolidate code changes, capture memory, apply learnings, and produce a final end-of-session report.

Do I need any dependencies to run the end-of-session report generation?

No dependencies are required to run the end-of-session report generation. The Skill operates independently to coordinate the four-phase wrap-up, enforce Korean Conventional Commits, and generate the final shareable report without external components.