mvt-cleanup

Inventory workspace artifacts, estimate token savings, and archive completed changes after confirmation.

19|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/uoyoCsharp/My-Virtual-TechTeam --skill mvt-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mvt-cleanup
Source: https://github.com/uoyoCsharp/My-Virtual-TechTeam/tree/main/.claude/skills/mvt-cleanup
Command: npx skills add https://github.com/uoyoCsharp/My-Virtual-TechTeam --skill mvt-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps clean up an AI project workspace after work accumulates across multiple change artifacts, session records, and legacy folders. It reduces context bloat, preserves useful summaries, and prevents completed work from making future sessions slower and harder to manage.

Core Features & Use Cases

  • Artifact Inventory and Cleanup Planning: Scans workspace artifacts, estimates token footprint, and classifies items such as active work, completed changes, unindexed directories, and legacy patterns.
  • Safe Archiving with Confirmation: Summarizes completed changes into a summary file, archives old artifact directories, truncates stale history, and always asks before destructive actions.
  • Workflow Integrity Checks: Warns when completed changes have not yet been synced, protects active changes from accidental cleanup, and handles epic-child archive relationships carefully.
  • Use Case: After several completed features and reviews have piled up in the shared workspace, use this Skill to reclaim tokens, archive finished change records, and keep only the most relevant active context available.

Quick Start

Ask the AI to run mvt-cleanup to review workspace artifacts, show a cleanup plan, and archive completed changes after confirmation.

Frequently Asked Questions about mvt-cleanup

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

FAQPage Schema
How do I clean up AI workspace artifacts and reduce token usage?

Workspace cleanup reduces token bloat by inventorying artifact directories, generating summary files for completed changes, and atomically moving stale items into an archive. This preserves session integrity while reclaiming context space.

What is the best way to archive completed changes in a persistent development workspace?

Archiving completed changes involves generating summary files and moving old artifact directories atomically. This approach carefully handles epic-child relationships and protects active changes from accidental cleanup.

How does workspace cleanup handle unsynced artifacts and epic tracking records?

Workspace cleanup handles unsynced artifacts by performing workflow integrity checks. It warns when completed changes have not been synced and carefully manages epic-child archive relationships before executing destructive actions.

Can I truncate stale session history without losing essential summaries?

You can truncate stale session history without losing essential summaries. The cleanup process generates summary files for completed work before archiving legacy folders, preserving useful context while updating session state consistently.

Does workspace cleanup require confirmation before deleting legacy folders?

Workspace cleanup requires confirmation before deleting legacy folders or taking destructive actions. It estimates token savings and classifies items as active work, completed changes, or legacy patterns, ensuring you approve the archival plan.

When should I avoid running an AI workspace artifact cleanup?

Avoid running an AI workspace artifact cleanup when you have active changes in progress or unsynced completed work. The process protects active work, but unsynced artifacts require syncing first to prevent data loss.