cleanup-copy

Delete merged project copies and associated Git remotes after validating merge status.

1|1|Updated Feb 1, 2026

Search Tags:#git #project management #development workflow #cleanup #code management

Ready to run

npx skills add https://github.com/corbat-tech/coco --skill cleanup-copy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cleanup-copy
Source: https://github.com/corbat-tech/coco/tree/main/.claude/skills/cleanup-copy
Command: npx skills add https://github.com/corbat-tech/coco --skill cleanup-copy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the safe removal of isolated project copies after their changes have been successfully merged back into the main project, preventing clutter and potential data loss.

Core Features & Use Cases

Automated Cleanup: Deletes temporary project copies created for feature development.
Safety Checks: Validates merge status and checks for uncommitted changes before deletion.
Reference Management: Cleans up associated Git remotes in the original project.
Use Case: After completing a feature branch, merging it back, and verifying the integration, you can use this skill to cleanly remove the development copy of the project.

Quick Start

Run /cleanup-copy followed by the name of the feature branch that was merged.

Frequently Asked Questions about cleanup-copy

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

FAQPage Schema

How do I safely delete project copies after merging a feature branch?▼

To safely delete project copies after merging, validate the merge status and check for uncommitted changes in the copy before removal. This automated cleanup also removes associated Git remote references from the original project.

What happens to Git remotes when I clean up merged feature branch copies?▼

When cleaning up merged feature branch copies, the associated Git remote references in the original project are deleted. This reference management prevents clutter after the isolated development copy is safely removed.

Can I remove an isolated project copy that still has uncommitted changes?▼

You cannot safely remove an isolated project copy with uncommitted changes. The cleanup process checks for uncommitted changes in the copy before removal to ensure no local modifications are lost during deletion.

How do I clean up temporary development workflow copies using a feature name?▼

To clean up temporary development workflow copies, run the cleanup command followed by the specified feature name. This identifies the correct copy directory and remote name to validate and remove after merging.

Why should I use an automated cleanup process for merged Git branches?▼

Using an automated cleanup process for merged Git branches prevents clutter and potential data loss. It validates merge status and safely deletes the temporary copies, ensuring your code management workflow remains organized.