land-changes

Coordinate branch preparation, PR creation, merge decisions, and cleanup for verified code.

Updated Aug 23, 2026

Search Tags:#verification #merge #guardrails #branch-management #pull-request #code-integration #land-changes

Ready to run

npx skills add https://github.com/caseyrtalbot/claude-plugins --skill land-changes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: land-changes
Source: https://github.com/caseyrtalbot/claude-plugins/tree/main/plugins/forge/skills/land-changes
Command: npx skills add https://github.com/caseyrtalbot/claude-plugins --skill land-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates the final integration process for verified code, ensuring branch preparation, PR creation, merge decisions, and post-landing cleanup with explicit user consent.

Core Features & Use Cases

Branch preparation and environment readiness
PR creation, merge decisions, and cleanup after landing
Guarded decision points with four explicit options for landing strategy

Quick Start

Prepare the integration branch, present four landing options, and execute the user’s chosen path (merge, PR, keep, or discard).

Frequently Asked Questions about land-changes

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

FAQPage Schema

How do I safely merge verified code changes into a main branch?▼

Safely landing verified code requires explicit user consent at guarded decision points. This skill coordinates branch preparation, pull request creation, merge decisions, and post-landing cleanup across standard Git workflows to ensure safe integration.

What are the options for landing code changes after verification passes?▼

After verification passes, you can choose from four explicit landing options: merge, pull request, keep, or discard. The skill presents these guarded decision points to guide your chosen integration path safely.

Does this code integration workflow require verification evidence before merging?▼

Yes, the workflow enforces verification evidence gating before proceeding. It requires verification proof to ensure only verified code progresses to branch preparation and the final merge decision stage.

How do I manage branch preparation and cleanup for pull requests?▼

Branch preparation and environment readiness are handled before pull request creation, followed by post-landing cleanup. This ensures the integration branch is properly staged and cleaned up after the merge decision.

Can I use this workflow to discard verified code without merging?▼

Yes, discarding verified code without merging is supported as one of the four explicit landing options. You can safely abort the code integration and remove the prepared branch while maintaining post-verification guardrails.