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.
curl -O https://raw.githubusercontent.com/ayutaz/piper-plus/dev/.claude/skills/check-pr-ready/SKILL.mdgit clone --depth 1 https://github.com/ayutaz/piper-plusWrote 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.
[](https://agentmods.dev/skills/ayutaz/piper-plus/check-pr-ready)<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="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.01305 |
| Opus 5 | $0.00024 | $0.00652 |
| Sonnet 5 | $0.00010 | $0.00261 |
| Haiku 4.5 | $0.00005 | $0.00130 |
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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 103 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: ブランチと未コミット確認
- ブランチが
dev以外であることを確認 - 未コミット変更があれば、ユーザーに確認して
/commitを促す - dev との差分が 1 コミット以上あることを確認 (空の PR を防ぐ)
Phase 2: コードチェック
$ARGUMENTS に skip-tests が 含まれていない 場合のみ、以下を実行:
/precheckskill を実行 (lint + format + test)- 実装: precheck と同じロジックを直接実行 (lint + format + scope-detected tests)
- 失敗があれば即停止し、修正案を提示
Phase 3: ドキュメント整合性チェック
-
CLAUDE.md 更新確認:
git diff dev..HEAD --name-onlyで大きな機能追加 (50 行以上の新規ファイル) を検出- 検出された場合、
CLAUDE.mdが同じ PR で更新されているか確認 - 未更新なら警告 (機能の追加箇所と CLAUDE.md のセクション提案)
-
README 更新確認:
- 同様に、README.md / src/python_run/README.md / src/wasm/openjtalk-web/README.npm.md を確認
- 機能名や API が変わっている場合は更新を促す
-
CHANGELOG 更新確認:
CHANGELOG.mdの Unreleased セクションが更新されているか確認- 大きな機能追加なら未更新を警告
-
docstring カバレッジ確認 (Python の場合):
git diff dev..HEAD --name-only -- 'src/python_run/piper_plus/*.py' 'src/python/g2p/*.py'- 新規 public 関数/クラスに docstring があるかチェック (簡易)
Phase 4: PR 本文ドラフト
- 上記すべてが OK なら、PR 本文のドラフトを生成:
- タイトル: dev..HEAD の最初のコミット件名 (70 文字以内)
- Summary: 各コミットの要約から 3-5 個の bullet
- Test plan: 実行したチェックの結果 checklist
- 形式は
gh pr create --body "$(cat <<'EOF' ... EOF\n)"で渡せる Markdown
Phase 5: 最終判定
- すべて緑 → 「PR 作成準備完了」と報告し、
gh pr createコマンドの提案を出力 - 1 つでも警告/失敗 → 修正項目をリスト化、緑にしてから再実行を促す
報告フォーマット
## PR Ready Check 結果
### Phase 1: ブランチ
- [x] ブランチ: feat/xxx (dev ではない)
- [x] 未コミット: 0 件
- [x] dev との差分: 5 コミット
### Phase 2: コードチェック
- [x] Python ruff check
- [x] Python ruff format
- [x] Python pytest (212 passed)
- [x] WASM npm test (481 passed)
### Phase 3: ドキュメント
- [x] CLAUDE.md 更新済み
- [x] README 更新済み
- [ ] ⚠️ CHANGELOG.md Unreleased 未更新
### Phase 4: PR 本文ドラフト
(生成された PR 本文)
### 判定: ⚠️ 1 件の警告あり (CHANGELOG)
修正してから再実行してください。
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.
- 8d ago First seen · 103 lines · 49 tokens per session scan A c3a7479169a9
check-pr-ready is a skill published in the GitHub repository ayutaz/piper-plus (204 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 1,305 once invoked, about $0.0002 per session on Opus 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.
Other skills, from other repositories
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
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.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
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…