skills.rest
floeorg
floeorgOFFICIAL
Explore all skills by this author →
GitHub

land

Close issues, remove worktrees, and sync main after merged PRs.

7|Updated Mar 13, 2026
Search Tags:#automation#git#cleanup#worktree#merge#post-merge
One-click install
npx skills add https://github.com/floeorg/floe --skill land-floeorg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land
Source: https://github.com/floeorg/floe/tree/main/.claude/skills/land
Command: npx skills add https://github.com/floeorg/floe --skill land-floeorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clean up after a merged PR: close the issue, remove the worktree, and sync main.

Only run this after the user confirms the PR has been merged.

Core Features & Use Cases

  • Close the issue when the PR is merged
  • Remove the worktree and tidy up local state
  • Sync main and verify epic sub-issues status if applicable

Quick Start

Tell Land to close the issue, remove the worktree, and sync main after you confirm the PR merge.

Frequently Asked Questions about land

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

FAQPage Schema
How do I automate Git post-merge cleanup for worktrees and issues?▼

You can automate Git post-merge cleanup by running sequential guarded steps that close linked issues, remove worktrees, and sync the main branch. This handles downstream housekeeping deterministically after a PR merge.

What is the best way to sync main and remove worktrees after a PR merge?▼

The best way to sync main and remove worktrees after a PR merge is using deterministic task orchestration. This approach infers branch-name context to safely execute local state tidy-up and repository synchronization.

How does branch-name context inference work for epic status checks?▼

Branch-name context inference works by parsing Git branch naming conventions to identify associated epics. It then verifies epic sub-issues status automatically during the post-merge workflow cleanup process.

Can I automate issue closure and epic sub-issue verification for collaborative Git projects?▼

Yes, you can automate issue closure and epic sub-issue verification for collaborative Git projects. The workflow applies guarded sequential execution to close merged PR issues and verify epic sub-issue statuses.

When should I run post-merge cleanup automation?▼

You should run post-merge cleanup automation only after confirming the PR has been successfully merged. Running it prematurely risks orphaning branches or closing issues before the code is integrated into the main branch.

Does post-merge cleanup require specific dependencies to sync main and close issues?▼

Post-merge cleanup to sync main and close issues does not require external dependencies. It operates using standard Git branches and built-in task orchestration to manage the sequential housekeeping workflow.

Related Skills

Explore More Software Engineering Skills→
thavirak-svaythavirak-svay
1

finishing-a-development-branch

Verify tests and present merge, pull request, or cleanup options for a git branch.

Community
Intermediate
zhayujiezhayujie
46.4k

openai-image-vision

Analyze images via OpenAI Vision API using Bash and curl.

Community
Intermediate
boparaiamritboparaiamrit
5

git-workflow

Enforce atomic commits, feature branches, and pull requests for Git workflows.

Community
Advanced
kirvinkirvin

sync

Fetch upstream changes and rebase the current Git branch onto them.

Community
Intermediate