review

Creates a non-auto-merging pull request from a feature branch to preprod for human review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams using an automated branch-and-release harness need a way to pause automation and put a human in the loop before code lands on preprod. This Skill opens a pull request that explicitly skips auto-merge so reviewers can inspect changes first. ## Core Features & Use Cases - Review-gated PR creation: Writes a .pr-description.md signal file with review: true frontmatter so the GitHub Actions workflow opens the PR without auto-merging it. - Docs audit before review: Launches a docs-updater agent against the preprod diff so stale documentation and missing ADRs are caught before humans review. - Structured PR body: Generates summary, spec link, code-review findings, technical changes, test steps, and the Railway preview URL so reviewers can verify the feature live. - Use Case: After finishing a feature on a claude/ session branch, run /review to open a PR to preprod, assign configured reviewers, and hand off to teammates who can later land it with /to-preprod. ## Quick Start Submit my current feature branch for team review by creating a pull request to preprod without auto-merge.

Frequently Asked Questions about review

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

FAQPage Schema
How do I create a pull request without auto-merge in GitHub Actions?▼

Write a .pr-description.md signal file with review: true in its frontmatter and push it on your branch. The harness workflow reads that flag, opens the PR to preprod, and skips the auto-merge step so humans review first.

How do I submit a feature branch for team review?▼

Run /review from the feature session. It resolves the feature name, diffs against origin/preprod, runs a documentation audit, writes the PR description with code-review findings, and pushes so the workflow opens the PR.

What is the difference between /review and /to-preprod?▼

/review opens a PR that stays open for human approval and merges nothing. /to-preprod creates or reuses a PR that auto-merges into preprod, and it is also the command used to land a PR after review approval.

Can reviewers test the feature before approving the PR?▼

Yes. The skill reads the Railway preview URL stored in the feature branch's .railway-url file and embeds it in the PR body, so reviewers can exercise the live preview environment while the PR waits.

What happens after the review is approved?▼

An approved PR is landed by running /to-preprod, which reuses the open PR, refreshes it, and cleans up the feature context. Clicking the GitHub merge button also works because a cleanup workflow removes leftover context from preprod.