ralph-discard

Discard RALPH worktrees and their uncommitted changes without merging.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/doravidan/supreme-ralph --skill ralph-discard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-discard
Source: https://github.com/doravidan/supreme-ralph/tree/main/templates/global/skills/ralph-discard
Command: npx skills add https://github.com/doravidan/supreme-ralph --skill ralph-discard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Abandon RALPH worktrees and all their changes without merging, preventing clutter and accidental merges.

Core Features & Use Cases

  • Discard a single RALPH worktree without affecting others.
  • Discard all RALPH worktrees in one operation.
  • Handle uncommitted changes with optional confirmation to avoid data loss.

Quick Start

Use the ralph-discard command to remove the active worktree or specify a worktree name to target a specific one. Example: /ralph-discard or /ralph-discard user-authentication --force

Frequently Asked Questions about ralph-discard

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

FAQPage Schema
How do I safely discard a git worktree and its uncommitted changes?

To safely discard a git worktree, you can use a dedicated cleanup command that removes the worktree and abandons its changes without merging, preventing accidental data integration. Optional force flags handle uncommitted modifications.

How do I remove multiple worktrees at once without merging their branches?

Removing multiple worktrees at once is supported by operations that discard all targeted worktrees and their changes in a single action. This prevents clutter and ensures no unwanted branch merges occur during the cleanup process.

What is the best way to clean up abandoned feature branches and worktrees?

The best way to clean up abandoned feature branches and worktrees is using a discard operation that safely deletes the worktree and its changes without merging. This prevents repository clutter and avoids accidental integration of incomplete work.

Can I force delete a worktree if it has uncommitted changes?

Yes, you can force delete a worktree with uncommitted changes by using a force flag. This bypasses standard confirmation prompts to ensure the worktree and all its local modifications are permanently discarded without merging.

When should I discard a worktree instead of merging it?

You should discard a worktree instead of merging when the feature branch is no longer needed or the changes are obsolete. Discarding safely removes the worktree and prevents unwanted or accidental merges of abandoned code into your main branch.

Related Skills