to-preprod

Triggers auto-merge of a feature branch into preprod via a signal file and GitHub Actions.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Evolutionary-Leadership/harness --skill to-preprod-evolutionary-leadership
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-preprod
Source: https://github.com/Evolutionary-Leadership/harness/tree/main/.claude/skills/to-preprod
Command: npx skills add https://github.com/Evolutionary-Leadership/harness --skill to-preprod-evolutionary-leadership

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging a finished feature branch into the preprod staging branch involves PR creation, conflict resolution, documentation audits, and cleanup; this Skill automates that entire gate by pushing a signal file that a GitHub Action turns into an auto-merged PR. ## Core Features & Use Cases - Signal-based auto-merge: Writes and pushes a .pr-description.md signal file so the GitHub Action opens and auto-merges the PR from feature/<name> to preprod, reusing any open /review PR. - Conflict pre-resolution: Merges preprod into the current branch locally first, with a documented discipline for resolving conflicts before they can stall the PR. - Docs and spec gating: Runs a docs-updater agent and, when a specification is connected, enforces a drift gate whose run records are committed as an auditable ledger. - Use Case: After finishing a feature on a claude/ session branch, invoke the skill to retire the feature context, generate a structured PR description, and hand the merge to CI without touching the GitHub UI. ## Quick Start Merge my current feature branch to preprod with the PR title "Add user notification preferences".

Frequently Asked Questions about to-preprod

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

FAQPage Schema
How do I merge a feature branch into preprod with GitHub Actions?

Run the /to-preprod skill from your claude session branch. It writes a .pr-description.md signal file, commits it with -f since the file is gitignored, and pushes; the GitHub Action then opens and auto-merges the PR from feature/<name> to preprod.

How do I resolve merge conflicts with preprod before opening a PR?

Merge origin/preprod into your current branch locally with git merge origin/preprod --no-edit before pushing. Resolve each conflicted hunk by reading both sides' intent, run the project's checks, then stage and commit so the PR merges cleanly.

Why did the to-preprod workflow fail with a PAT_TOKEN error?

The workflow fails fast when the PAT_TOKEN secret is missing or empty, since it needs repo and workflow scopes to create and merge PRs. Add the secret under Settings, Secrets and variables, Actions, then re-push the claude branch to retrigger the run.

What is the preprod gate and when does it block a merge?

The preprod gate runs only when a specification is connected via the spec_product key in .harness-version. In enforce mode it stops merges carrying new drift the branch introduced; in evaluate mode it reports the same rows but merges anyway.

Can I use to-preprod without the spec loop connected?

Yes. When spec_product is absent from .harness-version, the entire gate step is skipped and the skill performs only the merge, docs audit, context retirement, and PR description without mentioning the spec loop.