land-feature

Name: land-feature
Availability: InStock
Author: mckissinger

Coordinate GitHub pull request landing workflows to safely merge verified features into the main branch.

1|Updated Jun 29, 2026

Search Tags:#github #verification #branch management #pull requests #feature delivery #git merge

Ready to run

npx skills add https://github.com/mckissinger/keel --skill land-feature

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: land-feature
Source: https://github.com/mckissinger/keel/tree/main/skills/land-feature
Command: npx skills add https://github.com/mckissinger/keel --skill land-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents fragile feature merges by enforcing a reliable, user-controlled workflow for landing verified changes without breaking stacked pull requests or losing verification records.

Core Features & Use Cases

Stacked PR Coordination: Handles bottom-up merging, retargeting, branch cleanup, CI re-triggering, and recovery from stacked pull request failures.
Verification Preservation: Maintains verified-pin integrity through rebases, diamond milestone workflows, and post-merge consolidated checks.
Use Case: Use this Skill after a feature's milestones are implemented, verified, pinned, and reviewed to safely integrate the completed work into main while keeping Git history and validation trustworthy.

Quick Start

Use the land-feature skill to guide the approved merge of my verified feature pull requests into main.

Frequently Asked Questions about land-feature

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

FAQPage Schema

How do I safely merge verified feature branches into main without breaking stacked pull requests?▼

Merge stacked pull requests bottom-up to retarget dependent branches, re-trigger CI, and clean up branches sequentially. This controlled merge sequencing prevents fragile feature merges and keeps Git history trustworthy.

How do I preserve verification pin integrity through rebases before landing a feature?▼

Preserve verification pin integrity through rebases by applying controlled merge sequencing that maintains verified-pin records. This ensures validation gates and post-merge consolidated checks remain trustworthy during feature delivery.

What is the best way to manage milestone-based delivery when merging multiple feature pull requests?▼

Manage milestone-based delivery by coordinating diamond milestone workflows with controlled merge sequencing. This approach maintains verification gates and applies post-merge consolidated checks to validate integrated feature work safely.

Does this feature landing workflow support recovery from stacked pull request merge failures?▼

This feature landing workflow supports recovery from stacked pull request failures by coordinating branch cleanup, CI re-triggering, and retargeting dependent branches during controlled merge sequencing into main.

When do I need controlled merge sequencing for GitHub pull requests?▼

You need controlled merge sequencing when landing verified feature changes into main involves stacked pull requests, milestone-based delivery, or rebases. It prevents unsafe merging by enforcing verification gates and post-merge validation.