prepare-paperclip-pr

Featured

Prepare a Paperclip branch for PR with commits, template body, and checks.

AI & Automation 114,742 stars 19046 forks Updated today MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Prepare Paperclip PR The standard Paperclip procedure for turning branch work into a reviewed, green pull request against `paperclipai/paperclip` master. Apply it once per PR (if a task splits a branch into several PRs, run the whole procedure for each one). ## 0. Preconditions — worktree safety * Do all PR work in a **git worktree** on a dedicated branch. The main `~/paperclip` checkout typically runs the live Paperclip server — never check out branches there. If you are already on a worktree/branch, verify it (`git rev-parse --git-dir`, `git branch --show-current`) and proceed. * If the main checkout is unexpectedly off `master`, fix that first without losing work (usually: move that branch's work into a worktree). * Confirm which remote/ref you are targeting (normally `master` on the `paperclipai/paperclip` repo; the task may name a specific remote such as `origin` or `public-gh`). ## 1. Commit everything — lose no work * Make **logical commits** of all uncommitted changes before anything else. Do not stash and forget; do not leave files behind. If commits are missing, make them. * Commit messages must end with exactly: `Co-Authored-By: Paperclip <noreply@paperclip.ing>` ## 2. Get changes cleanly on top of master * Fetch the target remote and rebase (or otherwise replay) your branch on top of the target master so the PR has no merge conflicts. * Re-verify after rebase: build/tests relevant to the change still pass at whatever depth the task w...

Details

Author
paperclipai
Repository
paperclipai/paperclip
Created
8 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category