land

Commit changes, push to the remote, and open a pull request for handoff.

50|14|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill land-all-the-vibes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land
Source: https://github.com/All-The-Vibes/ATV-StarterKit/tree/main/.github/skills/land
Command: npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill land-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close out a session by committing changes, pushing them, and opening a pull request for handoff. This ensures a formal handoff trail and prevents silent loss of work.

Core Features & Use Cases

  • End-to-end landing workflow: commit, push, and open a PR for handoff (without merging).
  • Safety guardrails: a PR is required for review and human approval; landing does not merge automatically.
  • Works across typical repo layouts and supports handoff between agents and humans in collaborative sessions.

Quick Start

Run the land routine at the end of a session to finalize work, create a PR, and prepare for handoff.

Frequently Asked Questions about land

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

FAQPage Schema
How do I automate git workflow to create a pull request for handoff?

Automate a git handoff workflow by committing changes, pushing to the remote, and opening a pull request. This formalizes the code review process without merging automatically. It ensures a formal handoff trail and prevents silent loss of work.

What is the best way to wrap up a coding session across repositories?

The best way to wrap up a coding session is running an end-to-end landing routine that commits changes, pushes them, and opens a PR to prepare a handoff summary for the next actor. This works across typical repo layouts to formalize review.

Does this pull request workflow merge code automatically?

No, this pull request workflow does not merge code automatically. It enforces safety guardrails by requiring a PR to exist for human review and approval before any merging occurs.

Can I use this to hand off work between agents and humans?

Yes, you can use this to hand off work between agents and humans. The workflow prepares a handoff summary and opens a pull request for collaborative sessions across typical repo layouts.

Why does my session need a pull request before finishing?

Your session needs a pull request before finishing to prevent silent loss of work. It enforces that a PR exists and the push succeeds to ensure a formal handoff trail for the next actor.