wrapup

Writes session logs, updates memory files, and syncs unpushed git work at session end.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/joydai2026-del/skills --skill wrapup-joydai2026-del
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wrapup
Source: https://github.com/joydai2026-del/skills/tree/main/wrapup
Command: npx skills add https://github.com/joydai2026-del/skills --skill wrapup-joydai2026-del

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? End-of-session work is easy to lose: session logs go unwritten, working memory grows stale, corrections never get promoted to durable patterns, and finished commits sit unpushed on local branches. This Skill enforces a complete, mandatory end-of-session protocol so nothing from a working session is silently dropped. ## Core Features & Use Cases - Thirteen mandatory outputs: session log, session index, context update, corrections log, decision files, pattern promotion, plan archival, vault overview sync, skill self-improvement, usage tracking, skills sync to remote, unpushed-work sweep, and next-session prompt generation. - Unpushed-work sweep: expands every git worktree and lists branches with no upstream or unpushed commits, catching work that git status on a single checkout cannot see. - Token-budgeted working memory: estimates memory file cost as (CJK chars / 1.3) + (other chars / 4) and fails the check when over budget, forcing compression in the same wrap-up. - Use Case: At the end of a long coding session spanning multiple repos, invoke the wrap-up to log what happened, dual-write corrections to the shared memory store, publish safe unpushed branches, and generate a prompt for the next session. ## Quick Start Tell the agent to wrap up this session and run the full end-of-session protocol including the unpushed-work sweep.

Frequently Asked Questions about wrapup

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

FAQPage Schema
How do I save an AI agent session's work before closing it?▼

Run the wrap-up protocol, which writes a session log, updates the session index and context files, records corrections and decisions, and generates a next-session prompt. All thirteen outputs are mandatory, so nothing is skipped.

How do I find unpushed commits across multiple git worktrees?▼

Use git worktree list --porcelain to expand every worktree, then run git for-each-ref on each to list branches with no upstream or unpushed commits. A branch with an empty upstream column has never reached the remote and is the highest priority to publish.

Why does git status show a clean tree but work is still lost?▼

git status reports only one checkout, so branches in other worktrees or with no remote tracking stay invisible. The wrap-up's unpushed-work sweep checks every worktree and branch explicitly to catch this case.

Why does git push origin main keep failing on a long-lived repo?▼

The checkout is usually on a feature branch, so the push targets a stale local main ref. Check git symbolic-ref --short HEAD first, and push explicitly with git push origin HEAD:refs/heads/main instead of resetting hard.

How should agent working memory be size-limited?▼

Use a token budget, not a line or byte count, estimated as (CJK characters / 1.3) + (other characters / 4). When over budget, archive the current file and rewrite it as short per-project blocks in the same wrap-up.

What are the limitations of this end-of-session protocol?▼

It assumes a specific environment: a notes vault, per-agent memory directories, a shared memory store with append and reconcile commands, and git-based projects. Without that setup, several of the thirteen mandatory outputs have no target to write to.