Skill · Land and release
/land$land@planr-land
Check whether reviewed work is ready to merge, publish, or deploy, and get the landing sequence in order. Land prepares the steps and never runs them.
/landin Claude Code. If /land runs another command, use /planr:land.
$landin Codex. With the OpenPlanr plugin for Codex, use $planr:land.
@planr-landin Cursor. Cursor applies the planr-land rule when you mention it in chat.
What it does
Assess release readiness and prepare or inspect an OpenPlanr landing sequence. Use after implementation and checks are complete, before merge, publication, or deployment.
Use Land after implementation and checks are complete. It reads the current branch, the worktree, the requested target, the checks that already ran, and the release constraints in the repository. It uses openplanr land only when that adds useful local state.
The reply gives readiness (ready, conditional, or blocked), the blockers, the ordered landing sequence with its preconditions, recovery guidance for the first meaningful failure, and one next action. Merging, publishing, and deploying stay with you. See Review before it lands.
When to use it
Use it to
- Prepare or inspect a landing and release plan
- Check whether reviewed work is ready to land without deploying it
Not for
- Build a new application feature
- Deploy or publish immediately
Example
/land the sign-in work on this branch$land the sign-in work on this branch@planr-land the sign-in work on this branchPrompts and commands
Check a branch is ready to land
Assess release readiness without merging, publishing, or deploying anything.
Prepare the merge and deploy steps
Get the ordered landing commands, their preconditions, and the recovery step for the first failure.
Apply pinned design feedback
Revise only the screens your review pins point at, and keep everything else as it was.