landlisted

# Land Workflow Use this skill when the user asks the AI to land work end to end. ## Contents - [At A Glance](#at-a-glance) - [What This Is Not](#what-this-is-not) - [Trigger Rules](#trigger-rules) - [Preconditions](#preconditions) - [Default Path](#default-path) - [Stop Conditions](#stop-conditions) - [Handoff](#handoff) - [Response Examples](#response-examples) ## At A Glance 1. Decide whether the current user message is approval to land. 2. Confirm branch, PR, checks, permissions, and local worktree state. 3. Merge using the repository or organization default merge method. 4. Sync local `main`, delete the verified topic branch, and restore any local-changes stash created for this workflow. 5. Report the result with the actual merge method and branch state. ## What This Is Not - Not a code review, test-fixing, or implementation workflow. - Not a ship workflow for creating branches, commits, pushes, or pull requests. - Not approval to merge from `main`, detached `HEAD`, or a branch without a matching pull request. - Not permission to bypass failing or pending checks unless the user explicitly forces landing in the current turn and the connected account can override repository protections. ## Trigger Rules - Treat a bare or direct current-turn command such as `land`, `land this`, `merge this PR`, or `land the current branch` as explicit approval to start the workflow without asking another confirmation question. - If `land` or `merge` appears as part of