Agent skill
cleanup-copy
Delete an isolated project copy after changes have been merged back. Use after merge-back is complete.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/cleanup-copy
SKILL.md
Cleanup Copy
Safely removes a forked project copy and cleans up any remaining git references.
What it does
- Validates the copy exists
- Warns if changes haven't been merged back (no
merge/<feature-name>branch found) - Warns if there are uncommitted changes in the copy
- Removes any leftover temporary remote in the original project
- Deletes the copy directory
- Lists remaining copies (if any)
Usage
/cleanup-copy <feature-name>
How to execute
This must be run from the ORIGINAL project directory (not the copy).
bash .claude/skills/cleanup-copy/scripts/cleanup-copy.sh "<feature-name>"
Important
- Always run
/merge-backBEFORE/cleanup-copyto avoid losing work - The script warns about unmerged changes but proceeds with deletion
- If you need to keep the copy, simply don't run this command
- Shows remaining copies after cleanup so you know what's still active
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?