القائمة
Prepare a Paperclip branch for PR with commits, template body, and checks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Write a short, colloquial summary for a Paperclip summary slot: open with the one or two decisions the reader must make — or, when nothing needs deciding, what to review — each with a recommendation, close with one or two recent pieces of work and where they stand, streaming status as it works.
Discover recently referenced Paperclip pull requests, mechanically verify their current-head readiness, drive non-draft PRs back to green through their originating issues, and publish a merge-confidence report without merging.
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
Run, verify, reseed, and repair Paperclip isolated dev workspace services. Use when asked to start or fix a managed project/worktree service and prove health, login readiness, cloned data, runtime visibility, and correct port ownership.
Add a new Paperclip issue-thread interaction kind end-to-end. Use when repo work introduces or extends interaction cards like request_confirmation, checkbox confirmations, ask_user_questions, or suggest_tasks.
Check a GitHub, GitLab, or Perforce PR/MR/CL for review comments, failing checks, and PR-body gaps. Use when asked to inspect, fix, or prepare a change for submission.
| name | prepare-paperclip-pr |
| description | Prepare a Paperclip branch for PR with commits, template body, and checks. |
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).
~/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.master, fix that first without
losing work (usually: move that branch's work into a worktree).master on the
paperclipai/paperclip repo; the task may name a specific remote such as
origin or public-gh).Co-Authored-By: Paperclip <noreply@paperclip.ing>pnpm-lock.yaml — the repo has actions that manage it.
If it is already in a commit, rewrite/drop that change before pushing..github/workflows/* unless the underlying commit was
explicitly about that and the task calls it out.CONTRIBUTING.md (repo root,
https://github.com/paperclipai/paperclip/blob/master/CONTRIBUTING.md) for
the PR title, message format, and issue description.gh.~ for home), Greptile score, and check status.pull_request work product for each opened PR (plus branch /
commit work products where the branch or a commit is itself the handoff).