land
Land
Take a pull request from "open and approved by the user" to "merged, released and recorded": its checks green on the head that merges, its release tagged on the merge commit, its deploys watched, the issues it closed shut and Done on the board.
Announce at start: "I'm using the land skill to merge #."
Run shell snippets in bash (Git Bash on Windows). .agents/skills/land/land.mjs reads the PR, its
checks, its release and its deploys, and prints one JSON object; it never writes. Board writes go
through .agents/skills/end-session/board.mjs, so end-session is installed beside this skill.
land never passes --admin or --auto, never changes a branch rule, never runs, re-runs or
dispatches a deploy or a migration, and never merges without a user to answer it. A blocked merge
is a finding to explain, never a rule to get past.