landing

Automate post-merge cleanup of worktrees, branches, and stale refs.

4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/danmestas/wardrobe --skill landing-danmestas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing
Source: https://github.com/danmestas/wardrobe/tree/main/skills/landing
Command: npx skills add https://github.com/danmestas/wardrobe --skill landing-danmestas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-merge cleanup can be error-prone and time-consuming. This workflow guides you through inventorying per-worktree changes, identifying what to keep or discard, and safely tidying local and remote branches, stale refs, and dist artifacts, while surfacing memory entries for review.

Core Features & Use Cases

  • Inventory per-worktree state and report items needing attention
  • Safely delete or preserve local/remote branches with guardrails
  • Prune stale remote refs and artifact directories (dist)
  • Surface today's memory entries for post-session review

Quick Start

Run the landing workflow to begin post-merge cleanup of your repository.

Frequently Asked Questions about landing

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

FAQPage Schema
How do I clean up local git branches after a merge?

To clean up local git branches after a merge, you can automate the process using a step-by-step workflow that inventories worktrees, prompts per-worktree decisions, and safely deletes merged branches with built-in safeguards to prevent data loss.

What is the best way to tidy git worktrees at the end of a development session?

Tidying git worktrees at the end of a development session involves inventorying per-worktree state, identifying items to keep or discard, pruning stale remote refs, and removing artifact directories to streamline your repository.

How do I prune stale remote refs and dist artifacts after merging a PR?

Pruning stale remote refs and dist artifacts after merging a PR is handled by a deterministic cleanup workflow that removes obsolete remote references and deletes artifact directories while preserving branches that have not been merged.

Does this post-merge cleanup workflow delete memory entries automatically?

Post-merge cleanup workflows do not automatically delete memory entries. The process surfaces today's memory entries for your manual review during the post-session maintenance phase, ensuring you retain important context.

Can I use this cleanup workflow to manage both local and remote branch deletions?

Yes, you can use this cleanup workflow to manage both local and remote branch deletions. It applies guardrails to safely delete or preserve branches based on your per-worktree decisions during the inventory process.

What safeguards are in place when pruning git branches and worktrees?

Safeguards when pruning git branches and worktrees include a deterministic, step-by-step workflow that inventories your current state and prompts per-worktree decisions before executing any local or remote branch deletions.