wrap-up

Scan and resolve orphaned resources, uncommitted git changes, and stale artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of session abandonment, where developers leave behind orphaned dev servers, uncommitted work, leaked simulators, and stale scratchpad files that consume system resources and create data loss risks.

Core Features & Use Cases

  • Deterministic Cleanup: Uses session-start timestamps to identify and clean up only the resources created during the current work session.
  • Safety-First Verification: Performs a multi-phase scan and validation process, including git state checks, port availability verification, and issue tracker synchronization.
  • Use Case: After finishing a complex feature implementation, run this skill to automatically commit your work, stop your local dev servers, clear temporary files, and verify that your issue tracker status is updated, ensuring your environment is perfectly clean for your next session.

Quick Start

Invoke the wrap-up skill by typing /wrap-up in your terminal when you are ready to finish your current work session.

Frequently Asked Questions about wrap-up

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

FAQPage Schema
How do I automate git cleanup and stop orphaned dev servers at the end of a work session?

Automating git cleanup and stopping orphaned dev servers requires a POSIX-compliant environment with git and standard system utilities to perform deterministic resource attribution and session cleanup. The wrap-up skill scans for and resolves uncommitted changes and leaked resources.

What is the best way to clean up stale development artifacts and uncommitted git changes?

The best way to clean up stale development artifacts and uncommitted git changes is a multi-phase scan and validation process. It performs git state checks, port availability verification, and issue tracker synchronization to ensure a consistent and safe exit state.

Does wrap-up work with issue tracking systems to synchronize status before finishing a session?

Yes, wrap-up works with issue tracking systems to synchronize status before finishing a session. It operates across git repositories, local dev servers, and issue tracking systems to automatically verify that your issue tracker status is updated.

How do I safely clean up only the system resources created during my current development session?

To safely clean up only resources created during your current development session, wrap-up uses session-start timestamps for deterministic cleanup. This identifies and cleans up only the resources created during the current work session, avoiding unintended data loss.

Do I need a specific environment to run automated session management and cleanup workflows?

You need a POSIX-compliant environment with git and standard system utilities to run automated session management and cleanup workflows. This environment is required to perform deterministic resource attribution and safely resolve orphaned system resources.

Why does session abandonment cause orphaned dev servers and stale scratchpad files to consume system resources?

Session abandonment causes orphaned dev servers and stale scratchpad files to consume system resources because developers leave behind uncommitted work and leaked simulators. This creates data loss risks and consumes system resources until a cleanup ritual is performed.