agentmods.dev

piper-plus: Skill for Claude Code

.claude/skills/check-pr-ready/SKILL.md

check-pr-ready is a skill for Claude Code from ayutaz/piper-plus. It costs 49 tokens per session (1,534 once invoked), scanned A, original, MIT.

A final checklist for deciding whether code is ready for a pull request, which is a request to merge changes into another branch. It checks the branch, uncommitted work, code quality, documentation, changelog, and relevant tests.

In plain words
What is it for?
Use it to run linting, formatting, and suitable tests, confirm the branch contains real changes, and check whether README files, developer instructions, changelog entries, or Python documentation need updates.
Why use it?
It catches unfinished changes and missing project updates before a pull request is opened. When a check fails, it stops and reports what needs attention.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md.

This is ayutaz/piper-plus's own configuration. It tells Claude Code how to work on piper-plus itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything piper-plus configures →

not rated 239repo +1 changed 3d ago A scan SkillSpector: pass 49 tokens original MIT
View source ↗ ayutaz/piper-plus ayutaz.github.io
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/check-pr-ready/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.

agentmods badge for check-pr-ready

README.md
[![agentmods](https://agentmods.dev/badge/skills/ayutaz/piper-plus/check-pr-ready/github.svg)](https://agentmods.dev/skills/ayutaz/piper-plus/check-pr-ready)
Your own site
<a href="https://agentmods.dev/skills/ayutaz/piper-plus/check-pr-ready"><img src="https://agentmods.dev/badge/skills/ayutaz/piper-plus/check-pr-ready/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.

agentmods 80×15 button for check-pr-ready

Your own site · 80×15
<a href="https://agentmods.dev/skills/ayutaz/piper-plus/check-pr-ready"><img src="https://agentmods.dev/badge/skills/ayutaz/piper-plus/check-pr-ready.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,534 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01534
Opus 5.5 $0.00020 $0.00614
Sonnet 5.5 $0.00010 $0.00307
Haiku 4.5 $0.00005 $0.00153

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

Security

Grade A, and why

check-pr-ready 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/check-pr-ready/SKILL.md · 106 lines

How it starts

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

PR 作成前 最終チェック

PR を出す前にすべての品質チェックを実行し、問題があればレポートします。 マージ可能な状態か判定する ことが目的です。

現在の状態

  • ブランチ: !git rev-parse --abbrev-ref HEAD
  • リモート差分 (dev との): !git log --oneline dev..HEAD 2>/dev/null | head -10
  • 未コミット: !git status --porcelain 2>/dev/null | head -20
  • 変更ファイル数: !git diff --name-only dev..HEAD 2>/dev/null | wc -l | tr -d ' '

実行手順 (順番通り、失敗したら停止して報告)

Phase 1: ブランチと未コミット確認

  1. ブランチが dev 以外であることを確認
  2. 未コミット変更があれば、ユーザーに確認して /commit を促す
  3. dev との差分が 1 コミット以上あることを確認 (空の PR を防ぐ)

Phase 2: コードチェック

$ARGUMENTS に skip-tests が 含まれていない 場合のみ、以下を実行:

  1. /precheck skill を実行 (lint + format + test)
    • 実装: precheck と同じロジックを直接実行 (lint + format + scope-detected tests)
  2. 失敗があれば即停止し、修正案を提示

Phase 3: ドキュメント整合性チェック

  1. CLAUDE.md 更新確認:

    • git diff dev..HEAD --name-only で大きな機能追加 (50 行以上の新規ファイル) を検出
    • 検出された場合、CLAUDE.md が同じ PR で更新されているか確認
    • 未更新なら警告 (機能の追加箇所と CLAUDE.md のセクション提案)

  2. README 更新確認:

    • 同様に、README.md / src/python_run/README.md / src/wasm/openjtalk-web/README.npm.md を確認
    • 機能名や API が変わっている場合は更新を促す

  3. CHANGELOG 更新確認:

    • CHANGELOG.md の Unreleased セクションが更新されているか確認
    • 大きな機能追加なら未更新を警告

  4. docstring カバレッジ確認 (Python の場合):

    • git diff dev..HEAD --name-only -- 'src/python_run/piper_plus/*.py' 'src/python/g2p/*.py'
    • 新規 public 関数/クラスに docstring があるかチェック (簡易)

Phase 4: PR 本文ドラフト

  1. 上記すべてが OK なら、PR 本文のドラフトを .github/pull_request_template.md の見出しどおりに生成:
    • タイトル: dev..HEAD の最初のコミット件名 (70 文字以内、 Conventional Commits の type(scope): ... 形式。 pr-metadata.yml の pr-title-check が検査する)
    • ## Summary: 各コミットの要約から 3-5 個の bullet
    • ## Affected Components / ## Type: 該当を - [x] で最低 1 個ずつ
    • ## Risk Level: patch / minor / major のうち ちょうど 1 個を - [x]
    • ## Contract Impact / ## Checklist / ## Related Issues: template の項目を埋める
    • ## Test Plan (大文字 P): 実行したチェックの結果 checklist。 空やコメントだけにしない
    • pr-metadata.yml の pr-body-validate step は Test Plan の中身、 Risk Level の 1 個、 Affected Components と Type の最低 1 個を検査し、 欠けると PR が red になる (詳細は /create-pr の「PR 本文フォーマット」)

Read the full file on GitHub · 106 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.

  1. 3d ago Changed · +3 lines 7300bffab600
  2. 2mo ago First seen · 103 lines · 49 tokens per session scan A c3a7479169a9

Subscribe to this mod's changes

check-pr-ready is a skill published in the GitHub repository ayutaz/piper-plus (239 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 1,534 once invoked, about $0.0002 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 reviewMultilingualPyTorchTestingdeep-learningjapaneseonnxspeech-synthesis
Related

Other skills, from other repositories

adk-go-self-review

Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…

google/adk-go · 87 tokens

adversarial-reviewer

Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…

emdash-cms/emdash · 72 tokens

go-testing

Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.

Gentleman-Programming/gentle-ai · 26 tokens

brooks-sweep

Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…

hyhmrright/brooks-lint · 178 tokens

plugin-review

Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.

athola/claude-night-market · 23 tokens

audit-ci

Run and analyze Elements cold CI performance profiles and propose evidence-backed build, test, lint, and dependency-graph improvements. Use whenever asked to profile or benchmark pnpm run ci, rerun ci:profile, create a CI performance audit, compare CI timings, find bottlenecks or the completion path, investigate a CI…

NVIDIA/elements · 78 tokens