land

Triages and merges all pending git branches, worktrees, and stashes into a local main.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/robritacca-dotcom/design-system --skill land-robritacca-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land
Source: https://github.com/robritacca-dotcom/design-system/tree/main/.claude/skills/land
Command: npx skills add https://github.com/robritacca-dotcom/design-system --skill land-robritacca-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When parallel sessions, parked experiments, and forgotten stashes pile up across branches and worktrees, it becomes unclear what is finished, what is superseded, and what is junk. This Skill sweeps every source of pending work in a git repository, judges each piece, and resolves all of it in one confirmed pass. ## Core Features & Use Cases - Full-repo sweep: Scans the working tree, worktrees, local and remote branches, and stashes, then reads each candidate's diff to classify it as finished, unfinished, superseded, or abandoned. - One-shot disposition: Presents a single table proposing land, keep, or delete for every candidate, with merge-conflict predictions via git merge-tree, and asks for one approval before acting. - Safe landing and disposal: Merges approved branches one at a time, regenerates generated files instead of hand-merging them, runs the full npm run verify on the combined result, and archives every deletion to a recoverable archive/* tag. - Use Case: After a week of parallel agent sessions, you have six branches, three worktrees, and a dirty working tree. Invoke the skill to get a triage table, approve the plan, and end with a verified local main carrying only the work worth keeping. ## Quick Start Ask the AI to land the work by combining all pending branches and worktrees into a local main without pushing anything.

Frequently Asked Questions about land

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

FAQPage Schema
How do I combine multiple git branches into main safely?

Sweep all branches, worktrees, and stashes, read each diff to judge whether the work is finished or superseded, then merge approved branches one at a time into a local main. Predict conflicts first with git merge-tree and verify the combined result before disposing of anything.

How do I clean up stale git branches and worktrees?

List unmerged branches and worktrees, check whether main has moved underneath each candidate, and classify them as keep or delete. Archive every deletion to a recoverable tag with git tag archive/<name> before removing the branch or worktree.

Does this skill push or deploy the merged work?

No, it never pushes and never deploys. Landing is deliberately local: the run ends with an unpushed main that passed verification, and taking it live is a separate explicit shipping step.

What happens to deleted branches, can they be recovered?

Every deleted candidate is archived to an archive/* tag before removal, which keeps the commits reachable permanently. Recovery is a single command: git checkout -b <name> archive/<tag>.

How are merge conflicts in generated files handled?

Generated files are never hand-merged. Either side is taken to get a resolvable tree, then the registry generator script rebuilds them from the merged sources, since a hand-merged generated file is wrong even when it looks right.

What happens if the final verification fails after merging?

Nothing is pushed, so nothing is broken publicly. The failing merge is identified and reported, and an unwind to the pre-land SHA via git reset --hard is offered but only executed after explicit confirmation.