defprod-change-land

Commits, merges, and pushes a reviewed change while stamping DefProd pipeline stages and completing delivered user stories.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/defprod1/defprod-skills --skill defprod-change-land-defprod1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: defprod-change-land
Source: https://github.com/defprod1/defprod-skills/tree/main/skills/defprod-change-land
Command: npx skills add https://github.com/defprod1/defprod-skills --skill defprod-change-land-defprod1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Landing a finished change involves more than a git push: commits need a correlation trailer so CI hooks can stamp later pipeline stages, merge and push operations must be recorded on the DefProd change, and delivered user stories must be advanced to completed. This Skill automates that final land stage of the DefProd change workflow so nothing downstream loses track of the change. ## Core Features & Use Cases - Correlation trailer commits: Appends the Change: <product-slug>/CHG-NN trailer to every commit so CI/CD hooks can resolve the change from a push range, including in multi-product monorepos. - Stage stamping around merge/push: Calls startChangeStage before and finishChangeStage after each merge or push it performs, reporting the driver (agent or human) and honoring the stage's consent mode. - Safe trunk integration: Integrates a diverged trunk via fast-forward or merge commit, never rebasing it, and uses git cherry to detect duplicate commits before merging. - Story completion: After a successful landing, evaluates every acceptance criterion on each linked user story and patches wholly delivered stories to completed via the DefProd MCP server. - Use Case: After the test stage passes on change CHG-12, invoke this Skill to commit with the trailer, merge the change branch into main, push to origin, stamp the merge and push stages, clear the worktree pin, and mark the delivered stories completed. ## Quick Start Ask the agent to land the current change by committing with the Change trailer, merging and pushing per the repo's flow, and completing its delivered user stories.

Frequently Asked Questions about defprod-change-land

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

FAQPage Schema
How do I land a DefProd change after the test stage passes?

Invoke the land stage to commit any uncommitted work with the Change trailer, then merge or push according to the repo's flow. The stage stamps startChangeStage before and finishChangeStage after each operation it performs, then advances delivered stories to completed.

What is the Change trailer in a commit message?

The Change trailer is a final commit line formatted as Change: <product-slug>/CHG-NN that correlates the commit with a DefProd change. CI/CD hooks use it to resolve the change from a push range and stamp later pipeline stages like build and ship.

Can this skill run standalone without the change orchestrator?

Yes, it works standalone by resolving change context from the .defprod/change pin, the branch name, or a trailer on the HEAD commit. Without a driver context it defaults to interactive mode and stops after committing to wait for merge or push consent.

Why does the land stage refuse to rebase the trunk?

Rebasing the trunk rewrites the commits every outstanding change branch was cut from, so merging those branches later duplicates history under new hashes. The stage integrates a diverged trunk with fast-forward or a merge commit and uses git cherry to detect duplicates.

When does the land stage mark a user story as completed?

A story is patched to completed only after the merge or push succeeds and every acceptance criterion is satisfied by landed or previously delivered work. Partially delivered stories stay at inProgress, and the outstanding criteria are named in the stage summary.

What happens if the worktree pin and branch disagree before committing?

The stage aborts loudly without committing, naming the expected versus actual branch and pinned change. This guard prevents work from landing on the wrong branch when concurrent change sessions repoint the worktree.