land

Enforce CI and branch-state checks before merging Git changes.

264|27|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/PacificStudio/openase --skill land-pacificstudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land
Source: https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/land
Command: npx skills add https://github.com/PacificStudio/openase --skill land-pacificstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land merges are risky when CI and branch-state checks haven't been validated. This skill provides guardrails and a concise checklist to ensure only reviewed changes are landed after CI green and the branch is up-to-date.

Core Features & Use Cases

  • Enforces pre-merge validation by requiring CI to be green before land actions.
  • Ensures branch synchronization with the mainline to preserve a linear history.
  • Records a traceable merge-ready state and checklist to support reviews and audits.

Quick Start

Land the change only after CI passes and the branch is synchronized with the main branch.

Frequently Asked Questions about land

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

FAQPage Schema
How do I safely merge a Git branch after CI passes?

To safely merge a Git branch after CI passes, enforce pre-merge validation that requires CI to be green and branch synchronization with the main branch to preserve a linear history.

What is a pre-merge check for landing code changes?

A pre-merge check for landing code changes is a validation step that confirms CI is green, the branch is up-to-date with main, and reviewer checks are passed before allowing a merge.

How do I keep my feature branch synchronized with the main branch before merging?

Keeping a feature branch synchronized with the main branch before merging requires validating the branch state against the mainline to ensure it is up-to-date and can maintain a linear history.

Does this Git workflow support maintaining a linear commit history during merges?

Yes, this Git workflow supports maintaining a linear commit history during merges by enforcing branch synchronization with the mainline before any land actions are permitted.

What gets recorded when a branch is ready to land after CI and review checks?

When a branch is ready to land after CI and review checks, a traceable merge-ready state and checklist are recorded to support subsequent reviews and audits.

Why do my merges break when the branch is not up-to-date with main?

Merges break when the branch is not up-to-date with main because the lack of synchronization disrupts linear history and bypasses the enforced pre-merge branch-state validation.