wrap-up

Commit changes, validate file placement, and log task progress at session end.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ItsMattG/property-tracker --skill wrap-up-itsmattg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap-up
Source: https://github.com/ItsMattG/property-tracker/tree/main/.claude/skills/wrap-up
Command: npx skills add https://github.com/ItsMattG/property-tracker --skill wrap-up-itsmattg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session routine ensures that all changes are committed, relevant memory is reviewed, and future tasks are properly tracked before you close the session.

Core Features & Use Cases

  • Phase 1: Ship It: Perform git status checks, auto-stage and commit meaningful changes (excluding sensitive/files), automatically fix misplacements per conventions, clean up completed beads tasks, and remind about worktree cleanup if merged.
  • Phase 2: Remember It: Extract insights from the session and persist them to memory, create CLAUDE rules if new patterns are discovered, and keep memory clean by flagging stale items.
  • Phase 3: Review & Apply: Produce a concise wrap-up report, summarize changes, and prepare the environment for the next session.

Quick Start

Run the wrap-up routine at the end of your session to finalize work and capture learnings.

Frequently Asked Questions about wrap-up

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

FAQPage Schema
How do I automate end-of-session git commits and housekeeping?

Automate end-of-session git commits by running a wrap-up routine that checks git status, auto-stages meaningful changes, commits them, and validates file placement. This ensures a clean working tree before shutdown while excluding sensitive files from the commit.

What is the best way to persist task progress and insights before closing a development session?

Persist task progress by extracting session insights and saving them to memory. This process captures learnings, creates rules for newly discovered patterns, and flags stale memory items to keep your task management context clean for future sessions.

Can I automatically fix file misplacements and clean up completed tasks before committing?

Yes, you can fix file misplacements automatically by validating changes against project conventions. The routine also cleans up completed tasks and reminds you to clean up git worktrees after a merge, ensuring a clean working tree.

How does deterministic task sequencing work during code changes?

Deterministic task sequencing works by applying a structured three-phase routine across development sessions: committing changes, persisting memory, and producing a concise wrap-up report that summarizes changes and prepares the environment for the next session.

Do I need any dependencies to automate post-session review and worktree cleanup?

No dependencies are required to automate post-session review and worktree cleanup. The routine runs independently to validate file placement, log task progress, and remind you of worktree cleanup if branches have been merged.

Why are my end-of-session commits missing newly discovered development patterns?

End-of-session commits miss new patterns when insights are not persisted. The routine solves this by extracting insights from the session, saving them to memory, and creating rules to capture newly discovered patterns for future reference.