land

Squash-merge approved GitHub PRs after pre-flight checks and log results.

16|2|Updated Mar 7, 2026

Search Tags:#automation #workflow #github #merge #pr #ci #land

Ready to run

npx skills add https://github.com/hojinzs/github-symphony --skill land-hojinzs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: land
Source: https://github.com/hojinzs/github-symphony/tree/main/.codex/skills/land
Command: npx skills add https://github.com/hojinzs/github-symphony --skill land-hojinzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge an approved PR during the Land state by ensuring pre-flight checks, squash merge, post-merge bookkeeping, and proper transition to Done.

Core Features & Use Cases

Pre-flight checks: at least one approval, green CI, and branch up-to-date.
Squash merge and post-merge bookkeeping with audit trail.
Transition to Done via gh-project and log results in the land workpad.
Use case: ready-to-land PRs in Land state are merged safely with compliance and traceability.

Quick Start

In Land state, run the land workflow to safely squash-merge an approved PR after pre-flight checks.

Frequently Asked Questions about land

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

FAQPage Schema

How do I safely merge an approved GitHub PR only after CI checks pass?▼

To safely merge an approved GitHub PR, the land workflow performs pre-flight checks to verify green CI, at least one human approval, and branch freshness before executing a squash merge.

What checks are required before merging a pull request during the Land state?▼

Before merging a pull request during the Land state, required pre-flight checks include at least one approval, green CI status, an up-to-date branch, and optionally verifying changeset presence.

How do I automate squash merging and track post-merge bookkeeping for GitHub projects?▼

Automate squash merging by using the land workflow to execute the merge, log audit trail results in the land workpad, and transition the project state to Done via gh-project for traceability.

Can I transition a GitHub project to Done automatically after a PR is squash merged?▼

Yes, you can transition a GitHub project to Done automatically after a PR is squash merged by using gh-project for state transitions while logging post-merge bookkeeping results in the land workpad.

Does merging a ready-to-land PR require a changeset before running the workflow?▼

Merging a ready-to-land PR optionally requires a changeset as part of the pre-flight checks, alongside mandatory requirements of at least one approval, green CI, and an up-to-date branch.

What is the best way to ensure compliance and traceability when landing approved pull requests?▼

The best way to ensure compliance and traceability when landing approved pull requests is to enforce pre-flight validation, perform a squash merge, and log post-merge bookkeeping in the land workpad.