Skip to content
cccskills
FreePublished on GitHubEnglish overview

prepare-paperclip-pr

Prepare Paperclip changes for a pull request by organizing commits, updating the branch, writing the description, addressing automated review feedback, and checking tests and CI before reporting the result for handoff.

OriginalShow the original description

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

paperclipai/paperclip
AI rating90/ 100See how to install

Good for

  • Preparing completed Paperclip changes for review
  • Resolving Greptile feedback and failed checks
  • Splitting large changes into separate pull requests
  • Reporting pull request links and handoff status

Overview

What it does

Turns changes on a Paperclip branch into a pull request with the information needed for review and handoff. It groups changes into meaningful commits, updates the branch against the target master, and resolves conflicts. The workflow covers writing a description that follows CONTRIBUTING.md, opening the PR with gh, fixing Greptile findings, and checking tests and CI.

When it helps

Use it after completing a Paperclip implementation to work through the preparation for review. It also helps split changes across multiple PRs when many files are involved, check for duplicate migration numbers, and hand off the work with its location and verification results.

Example requests

  • “Commit these changes, create a Paperclip PR, and work through the review and checks.”
  • “Count the changed files, split the PR if needed, and report each URL and its verification results.”

Notes

Assumes a dedicated branch and git worktree, plus gh, Greptile, /greploop, and /prcheckloop. Do not commit pnpm-lock.yaml. Each PR must contain fewer than 100 changed files. Verify a Greptile score of 5/5, no unresolved comments, and successful required checks.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Objective evaluation

AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.

Clear instructionsIs it clear when to use it and what it does?
AGoodIt clearly covers committing Paperclip changes, opening a PR, and completing review and checks.
Concrete stepsAre steps, inputs, outputs, and examples spelled out?
AGoodIt specifies commit formatting, the under-100-file limit, review completion criteria, and reporting fields.
SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt requires a dedicated worktree, restricts file changes, and prohibits force-pushes that discard work.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingIt assumes gh, Greptile, and company skills, but provides no installation or authentication steps.

The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 20, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md3.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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 warrants.

3. Guardrails checklist (every PR)

  • Never commit pnpm-lock.yaml — the repo has actions that manage it. If it is already in a commit, rewrite/drop that change before pushing.
  • Never change .github/workflows/* unless the underlying commit was explicitly about that and the task calls it out.
  • No design screenshots / wireframe images committed to the repo unless they are genuinely part of the work product.
  • Migrations: numbered incrementally with no conflicts against master. If master moved and took your number, renumber on top. Make migrations idempotent so users who already applied the old number are safe.
  • Greptile file limit: keep each PR under 100 changed files; if a PR exceeds that, split it into two.

4. Open the PR

5. Review loops

  • Run the /greploop company skill: trigger Greptile review, address its comments, push, and repeat until Greptile gives 5/5 with zero unresolved comments (max 20 turns). Do not stop early while turns remain.
  • Then run the /prcheckloop company skill and address any verification / CI failures you can.
  • RUN GREPTILE UNTIL IT GETS TO 5/5 - DO NOT STOP UNTIL GREPTILE IS 5/5, all tests pass, all verification checks pass, and there are no merge conflicts.

6. Report back and hand off

  • Comment on the driving task: what you did, the PR URL(s), the worktree path (use ~ for home), Greptile score, and check status.
  • Create a pull_request work product for each opened PR (plus branch / commit work products where the branch or a commit is itself the handoff).
  • If the task requires follow-up per PR (e.g. sub-issues per PR), create them as the task directs and link them.

Hard rules

  • Never lose work: no orphaned stashes, no dropped files, no force-pushes that discard commits.
  • Always post the URLs to every pull request you created.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

add-product-e2e-eval

FreeSummaryAI rating 90

Add or extend Paperclip end-to-end evaluations that exercise real browser workflows across the server, database, and runner. Define expected outcomes, check independent evidence, and connect results to the existing reporting pipeline for local or Daytona execution.

  • Adding an evaluation for a complete user workflow
  • Updating test data and outcome checks
  • Including screenshots and artifacts in evaluation reports
paperclipai/paperclip106.4KUpdated Oct 23, 2026

add-runner-eval

FreeSummaryAI rating 90

Add or extend Paperclip Runner evaluations that test real sessions against a mock control service. Define observable pass conditions, validate cases and run selections, and retain source revisions, evidence, and costs for authorized live runs.

  • Adding a focused Runner protocol evaluation
  • Testing grading rules with valid and invalid evidence
  • Updating evaluation selections and campaign membership
paperclipai/paperclip106.4KUpdated Oct 23, 2026

agent-browser

FreeSummaryAI rating 90

Use a real browser to verify web pages and apps through short, supervised interactions. Capture screenshots, inspect errors and network requests, and document reproducible steps for UI bugs or expected behavior checks.

  • Capture screenshots to verify UI changes
  • Read content rendered by JavaScript
  • Reproduce UI bugs and record errors
paperclipai/paperclip106.4KUpdated Oct 23, 2026

agentmail

FreeSummaryAI rating 100

Read email linked to assigned Paperclip tasks, send new messages or replies through an assigned AgentMail inbox, and check delivery outcomes. Follow task permissions and preserve retry identifiers to avoid duplicate sends.

  • Reading email context attached to an assigned task
  • Sending a new email from an assigned inbox
  • Replying to a specific message in a conversation
paperclipai/paperclip106.4KUpdated Oct 23, 2026

check-pr

FreeSummaryAI rating 80

Inspect proposed changes in GitHub, GitLab, or Perforce for review feedback, failed automated checks, and incomplete descriptions. It separates actionable findings from informational or resolved comments, then helps fix issues and close addressed review threads when requested.

  • Inspect a change before submission
  • Identify failed checks and required fixes
  • Organize human and bot review feedback
paperclipai/paperclip106.4KUpdated Oct 23, 2026

company-creator

FreeSummaryAI rating 100

Create an AI agent company or team package from an idea or an existing repository. Define roles, reporting lines, skills, and work handoffs, then generate structured files that follow the Agent Companies specification.

  • Build an agent company from an idea
  • Turn a repository into an agent team package
  • Define agent roles and work handoffs
paperclipai/paperclip106.4KUpdated Oct 23, 2026

See all skills by paperclipai

Report a problem with this skill