make-pr

Create and update GitHub pull requests using a validated PR body schema and stacked-branch workflow.

18|5|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill make-pr-neko-catpital-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-pr
Source: https://github.com/Neko-Catpital-Labs/Invoker/tree/main/skills/make-pr
Command: npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill make-pr-neko-catpital-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull request titles and bodies drift out of sync with the actual branch diff, and stacked PRs published through Mergify often ship with placeholder metadata. This Skill enforces a consistent, CI-validated PR schema so every published PR accurately describes its current diff. ## Core Features & Use Cases - Structured PR schema: Authors PR bodies with required sections (Summary, Review Claim, Review Lane, Review Unit, Safety Invariant, Slice Rationale, Non-goals, Test Plan, Revert Plan) that local validators check against the actual changed files. - Stacked PR management: Coordinates Mergify stack pushes, refreshes machine-managed stack comments, and audits live PR metadata after every restack or force-push. - Visual proof enforcement: Requires screenshots or video with manual inspection notes for UI-impacting diffs before publication. - Use Case: After splitting a large refactor into a stack of reviewable slices, run this Skill to validate each PR body against its diff, publish via node scripts/create-pr.mjs, and repair any Mergify placeholder titles before review. ## Quick Start Ask the AI to create a pull request for the current branch using the repo's preferred PR schema and validate the body against the current diff.

Frequently Asked Questions about make-pr

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

FAQPage Schema
How do I create a pull request with a validated PR body?

Copy the repo's pr-body-template.md, fill in the required sections, then run validate-pr-body-local.mjs against your base branch. Once validation passes, publish with create-pr.mjs, which uploads local proof images and creates or updates the PR.

How do I update a stacked PR after a force-push or restack?

Re-run the body validation against the current diff, then update each PR with create-pr.mjs --update-existing so titles, bodies, and the machine-managed stack comment stay in sync. Audit live PR metadata afterward to catch Mergify placeholder text.

When is visual proof required in a pull request?

Visual proof is required whenever the diff changes user-visible behavior, including UI files, window lifecycle, task status text, or workflow state shown in the app. State transitions need animated proof such as a gif or video, plus a manual inspection note.

Why does PR body validation reject my Review Lane or Review Unit?

The CI validator compares your declared lane and unit against the actual changed files and rejects mismatches, such as mixing behavior changes with docs or proof files. Split the branch into separate single-lane PRs rather than relabeling.

Can I run mergify stack push from a generated stack branch?

No. Running it from a Mergify-generated stack branch can publish an unrelated leftover stack. Always push from the working branch, preview with --dry-run first, or use the safe-stack-push.mjs guard script.