prepare-paperclip-pr

Automate the preparation and verification of pull requests for the Paperclip repository.

79.8k|14.6k|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/paperclipai/paperclip --skill prepare-paperclip-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepare-paperclip-pr
Source: https://github.com/paperclipai/paperclip/tree/main/.agents/skills/prepare-paperclip-pr
Command: npx skills add https://github.com/paperclipai/paperclip --skill prepare-paperclip-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the complex process of preparing a branch for a pull request, ensuring that all commits are logical, dependencies are managed, and quality checks are met before submission.

Core Features & Use Cases

  • PR Standardization: Enforces consistent commit messaging and branch management protocols.
  • Quality Guardrails: Automates checks for lockfile integrity, migration safety, and file count limits.
  • Review Orchestration: Manages the iterative review loop with Greptile and CI verification to ensure a green PR status.

Quick Start

Run the prepare-paperclip-pr skill to finalize your current branch for a pull request against the master branch.

Frequently Asked Questions about prepare-paperclip-pr

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

FAQPage Schema
How do I prepare a branch for a Paperclip PR?

Use the prepare-paperclip-pr skill to ensure your branch is rebased on master, commits are properly formatted, and all guardrails like file limits and migration safety are met.

What should I do if my PR exceeds the Greptile file limit?

The repository requires PRs to be under 100 changed files. If you exceed this limit, split your work into multiple smaller, logical pull requests.

Can I merge my own pull request?

No, you must never merge your own pull request. The procedure requires running the review loops and waiting for external verification and approval.

How do I handle migrations in my PR?

Migrations must be numbered incrementally and be idempotent. If master has moved, renumber your migrations on top of the current master to avoid conflicts.

Why should I use a git worktree for PR work?

Using a git worktree keeps your main checkout, which typically runs the live Paperclip server, safe from branch switching and potential work loss.