finish-worktree-lane

Attach a completed rt-scheduler worktree lane to a branch, stage by intent, commit with Lore trailers, push, and clean up.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/byonk19-svg/rt-scheduler --skill finish-worktree-lane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-worktree-lane
Source: https://github.com/byonk19-svg/rt-scheduler/tree/main/.cursor/skills/finish-worktree-lane
Command: npx skills add https://github.com/byonk19-svg/rt-scheduler --skill finish-worktree-lane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing a Codex or git worktree lane once work is completed requires wrapping up changes, consolidating work, and cleaning up resources to prevent drift and confusion.

Core Features & Use Cases

  • Attach a detached worktree to a stable branch, stage the lane's intent, and create a clean commit with Lore trailers.
  • Push the branch, open or merge a PR, and decommission the worklane by cleaning up the worktree and branch when done.
  • Applies to Codex-managed worktrees and standard git worktrees in collaborative software projects requiring end-to-end lane closure.

Quick Start

Finish a worktree lane by attaching it to a branch, staging by intent, committing with Lore trailers, pushing, opening or merging the PR, and cleaning up the worktree.

Frequently Asked Questions about finish-worktree-lane

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

FAQPage Schema
How do I finish a git worktree lane after completing work?

Finishing a worktree lane involves attaching the worktree to a stable branch, staging changes by intent, committing with Lore trailers, pushing the branch, opening or merging a PR, and cleaning up the worktree and branch.

What does it mean to stage changes by intent when closing a worktree?

Staging changes by intent means grouping related modifications into a clean, purposeful commit before pushing the branch. This ensures the pull request history remains organized and easy to review during lane closure.

Can I use this workflow to clean up both Codex and standard git worktrees?

Yes, this workflow applies to both Codex-managed worktrees and standard git worktrees in collaborative software projects. It requires proper branch naming conventions and preconfigured push and PR tooling to execute correctly.

What's the best way to attach a detached worktree to a stable branch for a pull request?

The best way to attach a detached worktree is to bind it to a stable branch, stage the lane's intent, and create a clean commit with Lore trailers. This establishes a clear reference point before pushing and opening a PR.

Why should I clean up the worktree and branch after merging a pull request?

Cleaning up the worktree and branch after merging prevents drift and confusion from lingering resources. Decommissioning the worklane ensures the repository remains tidy and avoids conflicts with future worktree lanes.