An automated workflow for creating a pull request, a request to merge code changes into another branch. It pushes the branch, creates the pull request, watches its automated checks, and handles review conversations.

Use it when turning current code changes into a pull request, monitoring its checks, replying to review threads, and marking those threads resolved. It can also create the pull request without monitoring.

It keeps the stages of a pull request together, so checking CI and replying to reviewers are less likely to be skipped. CI means automated tests and other checks run by the repository.

How ayutaz/piper-plus configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ayutaz/piper-plus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ayutaz/piper-plus/dev/.claude/skills/create-pr/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ayutaz/piper-plus

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ayutaz/piper-plus/create-pr/github.svg)](https://agentmods.dev/skills/ayutaz/piper-plus/create-pr)

Your own site

<a href="https://agentmods.dev/skills/ayutaz/piper-plus/create-pr"><img src="https://agentmods.dev/badge/skills/ayutaz/piper-plus/create-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ayutaz/piper-plus/create-pr"><img src="https://agentmods.dev/badge/skills/ayutaz/piper-plus/create-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,356 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00103	$0.04356
Opus 5.5	$0.00041	$0.01742
Sonnet 5.5	$0.00021	$0.00871
Haiku 4.5	$0.00010	$0.00436

Measured 3d ago against content hash fa945c5ac72b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/create-pr/SKILL.md · 244 lines

How it starts

The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PR 作成 + CI 監視 + レビュー対応 (end-to-end)

/create-pr 1 コマンドで PR ライフサイクル全体を完結する skill:

push → PR 作成 → CI 監視ループ → review thread 返信 + resolve → 報告

過去 /create-pr → /watch-pr → /reply-review を別々の skill 呼び出しで連鎖していたが、「次の skill を Skill ツールで呼べ」という散文 handoff は LLM が実行を飛ばすと工程が抜ける (PR #496 / #505 で発生)。本 skill は全工程を inline フェーズ として持ち、 skill 間 handoff をゼロにする。

単体利用: CI 監視のみ → /watch-pr <PR#>、 review 対応のみ → /reply-review <PR#>、 backlog 集計 → /check-review-backlog。これらは本 skill のフェーズ 5 / 6 と同一手順の standalone 版。

自動発動条件

「PR を作って / 出して」「pull request を作って」「この変更で PR にして」「branch を push して PR にして」

明示呼び出し: /create-pr / /create-pr <base-branch> / /create-pr --no-watch (PR 作成のみ、監視ループに入らない)

引数

$ARGUMENTS 空: base = dev (memory feedback_merge_caution: 通常 dev を base)
<base-branch>: 明示指定 (例: main)
--title <title>: title 上書き (デフォルトは最新コミット message から抽出)
--no-watch: フェーズ 5/6 (CI 監視・review 対応) を skip し PR 作成で終了

制約 (memory 参照)

マイルストーン非付与 (feedback_pr_no_milestones): --milestone を付けない。本文に「M1」等も書かない
auto-merge 禁止 (feedback_merge_caution): gh pr merge --auto 等を使わない。マージはユーザー判断
本文書き換えは body-file (feedback_pr_body_over_comments): 既存 PR 更新は gh pr edit --body-file。新規コメント追記しない。 review thread への reply はこの制約の対象外
--no-verify 禁止 (CLAUDE.md): hook bypass 系を使わない
review thread の自動 reply は SAFE 系のみ: stale / Copilot style noise のみ自動 reply+resolve。人間 reviewer・logic/security 指摘は user 判断 (フェーズ 6)

PR 本文フォーマット (重要 — テンプレート準拠必須)

PR 本文は .github/pull_request_template.md の必須セクションをすべて含むこと。 PR metadata workflow (.github/workflows/pr-metadata.yml) の pr-body-validate step が以下を検査し、欠けると PR が必ず red になる (PR #505 で発生した既知バグ — 旧フォーマットはこのゲートを通らなかった):

本文が空でない
## Test Plan セクションが存在し非空 (大文字 P。 ## Test plan は grep ^## Test Plan に不一致で fail。  コメントだけも fail)
## Risk Level セクションでチェックボックスがちょうど 1 個 - [x]
## Affected Components セクションでチェックボックス最低 1 個 - [x]
## Type セクションでチェックボックス最低 1 個 - [x]

Read the full file on GitHub · 244 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago Changed · +5 lines fa945c5ac72b
2mo ago First seen · 239 lines · 103 tokens per session scan A 1b1076539b11

Subscribe to this mod's changes

create-pr is a skill published in the GitHub repository ayutaz/piper-plus (239 stars, last pushed today), licensed MIT. It adds 103 tokens to every session and 4,356 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Git and workflow Multilingual PyTorch deep-learning japanese onnx speech-synthesis

github

GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…

opensquilla/opensquilla · 101 tokens

meta-codereview-current-diff

Read the current uncommitted diff, run three independent reviewers (safety + tests-coverage + style) in parallel, then arbitrate a single BLOCK / BLOCKWITHOVERRIDE / PASSWITHNOTES verdict. Use before commit when you want a multi-perspective second-opinion instead of a single-reviewer agent loop.

opensquilla/opensquilla · 73 tokens

review-trtmc-pr

Review a TensorRT-Model-Connect GitHub PR or local contributor branch against the current post-#1093 model-family isolation architecture, repository rules, behavioral correctness, third-party dependency and license obligations, and exact-head validation evidence. Use for contributor self-review before marking a PR…

NVIDIA/TensorRT-Model-Connect · 105 tokens

submit-github-pr

Use when publishing an existing TensorRT-Model-Connect change as a GitHub pull request. Verifies authenticated repository access, branch and diff scope, validation evidence, commit identity, reviewer-facing text, exact pushed head, and the created draft PR without merging it.

NVIDIA/TensorRT-Model-Connect · 58 tokens

write-git-messages

Draft, revise, or review Git commit messages, PR titles, PR descriptions, and squash or rebase merge messages. Use when Codex needs to summarize a diff for reviewers, convert rough notes into a commit or PR message, check a message against Git and Conventional Commits style, or prepare repository contribution text…

NVIDIA/TensorRT-Model-Connect · 75 tokens

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

Yeachan-Heo/oh-my-claudecode · 47 tokens

piper-plus: Skill for Claude Code