neb-ws-cleanup

Automate cleanup of completed NebCore workspaces with pending-change checks.

Updated Aug 23, 2026

Search Tags:#automation #git #devops #submodules #task-status #workspace-cleanup

Ready to run

npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-ws-cleanup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: neb-ws-cleanup
Source: https://github.com/nebinfra/nebcore-ai-skills/tree/main/neb-ws-cleanup
Command: npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-ws-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Cleaning up idle workspaces after task completion optimizes resource usage and reduces environmental noise in NebCore deployments.

Core Features & Use Cases

Automated evaluation of workspaces under ~/sources/workspaces/ to determine eligibility based on task status (done or cancelled) and absence of pending changes in root and submodules.
Safe deletion with multi-step checks including avoidance of platform-managed workspaces and a final verification pass.
Use Case: A completed task leaves no active changes; this skill automatically prunes its workspace to reclaim disk space and simplify environment maintenance.

Quick Start

Identify eligible workspaces, confirm no pending changes, and delete those with completed tasks.

Frequently Asked Questions about neb-ws-cleanup

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

FAQPage Schema

How do I safely delete completed workspaces with uncommitted submodule changes?▼

Workspace cleanup requires checking for pending changes in root and submodules before deletion. This skill verifies task status and excludes workspaces with uncommitted changes to ensure safe pruning.

How do I automate workspace cleanup for cancelled or done tasks?▼

Workspace cleanup automation evaluates directories under ~/sources/workspaces/ for done or cancelled task statuses. It then prunes eligible workspaces while excluding platform-managed environments and outputting a structured report.

What is the best way to prune idle workspaces without losing uncommitted changes?▼

Pruning idle workspaces safely involves a multi-step verification process. This skill checks task status, scans for pending changes in root and submodules, and performs a final deletion pass to prevent data loss.

Can I use automated workspace cleanup in NebCore environments with platform-managed directories?▼

Workspace cleanup in NebCore environments specifically excludes platform-managed directories. It evaluates task statuses and pending changes to safely delete only eligible workspaces.

Why does workspace cleanup fail when there are pending changes in git submodules?▼

Workspace cleanup fails on pending changes to prevent data loss. The skill checks root and submodule git status, ensuring no uncommitted modifications exist before allowing deletion of done or cancelled tasks.