dev-reset-workspace

Clean repository workspaces by removing stale branches and uncommitted changes.

36|6|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Nebulavenus/forge-gpu --skill dev-reset-workspace-nebulavenus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-reset-workspace
Source: https://github.com/Nebulavenus/forge-gpu/tree/main/.claude/skills/dev-reset-workspace
Command: npx skills add https://github.com/Nebulavenus/forge-gpu --skill dev-reset-workspace-nebulavenus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cleanly resets the repository workspace to a pristine main branch by removing stale branches, uncommitted changes, and lingering background tasks.

Core Features & Use Cases

  • Phase-driven workflow that guides you through stopping tasks, auditing changes, syncing with main, and cleaning up local branches.
  • Safe-by-default operations with prompts and an optional --force flag to bypass confirmations when desired.
  • Designed for post-merge cleanups, pre-start of new work, and every time the working tree becomes dirty.

Quick Start

Reset the workspace to a clean main branch.

Frequently Asked Questions about dev-reset-workspace

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

FAQPage Schema
How do I safely clean up a dirty Git workspace and reset to the main branch?

To safely reset your Git workspace, this automation stops lingering tasks, audits uncommitted changes, syncs with the main branch, and removes stale branches. It uses safe deletion rules and prompts before destructive actions.

What is the best way to automate post-merge branch cleanup locally?

Automating post-merge branch cleanup involves resetting the workspace to a pristine main branch by removing stale artifacts. This process enforces safe deletion rules and guides you through auditing changes and syncing repositories.

Can I skip confirmation prompts when resetting my repository workspace?

Yes, you can skip confirmation prompts when resetting your repository workspace by using the --force option. This bypasses safe-by-default prompts to quickly clean uncommitted changes and lingering local branches.

Does this workspace reset automation remove uncommitted changes safely?

Yes, this workspace reset automation removes uncommitted changes safely by applying a phase-driven workflow. It audits local status and prompts before deleting dirty changes, ensuring you do not lose unsaved work unexpectedly.

When should I reset my local repository workspace to a clean main branch?

You should reset your local repository workspace to a clean main branch during post-merge cleanup, before starting new work, or whenever the working tree shows dirty changes and lingering branches that need artifact removal.

What does a phase-driven workspace cleanup workflow do before syncing to main?

A phase-driven workspace cleanup workflow stops background tasks and audits uncommitted changes before syncing to main. This ensures a clean repository state by enforcing safe deletion rules prior to removing stale local branches.