delete-environment

Delete Docker resources, filesystem artifacts, and GitHub issue labels by environment ID.

Updated Jan 8, 2026

Search Tags:#automation #environment management #cleanup #docker #github issues #docker compose

Ready to run

npx skills add https://github.com/takemo101/compose-workflow --skill delete-environment

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: delete-environment
Source: https://github.com/takemo101/compose-workflow/tree/main/.opencode/skill/delete-environment
Command: npx skills add https://github.com/takemo101/compose-workflow --skill delete-environment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the complete removal of containerized environments, including Docker resources, filesystem artifacts, and associated GitHub issue labels, ensuring a clean slate after development or testing.

Core Features & Use Cases

Comprehensive Cleanup: Removes Docker containers, networks, and volumes.
Filesystem Removal: Deletes specified working directories or Git worktrees.
GitHub Issue Label Management: Updates issue labels to reflect the environment's removal.
Use Case: After completing a feature branch that used a dedicated Docker environment, use this Skill to tear down all associated resources, preventing clutter and potential conflicts.

Quick Start

Execute the delete environment script for the environment ID 'abc-123' and its associated directory '.worktrees/issue-123'.

Frequently Asked Questions about delete-environment

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

FAQPage Schema

How do I automate Docker environment cleanup after finishing a feature branch?▼

To automate Docker environment cleanup, you can use a script that targets a specific environment ID to remove containers, networks, and volumes. This ensures all associated Docker resources are deleted, preventing clutter and conflicts after testing.

What is the best way to remove Git worktrees and Docker containers together?▼

The best way to remove Git worktrees and Docker containers together is through an automated cleanup script that deletes specified working directories and tears down Docker resources based on an environment ID.

Can I update GitHub issue labels automatically when tearing down a container environment?▼

Yes, you can update GitHub issue labels automatically when tearing down a container environment. The cleanup process includes GitHub Issue Label Management to reflect the environment's removal status.

Do I need Docker and GitHub CLI to delete containerized environments?▼

Yes, you need both Docker and GitHub CLI installed to delete containerized environments. These tools are required to execute the scripts that remove Docker resources, filesystem artifacts, and GitHub issue labels.

Why does my Docker environment cleanup leave orphaned volumes and networks?▼

Docker environment cleanup may leave orphaned volumes and networks if the removal process is not comprehensive. A dedicated cleanup script ensures all identified Docker resources are fully deleted.

What filesystem artifacts are removed during container environment deletion?▼

During container environment deletion, the filesystem artifacts removed include specified working directories and Git worktrees associated with the target environment ID.