Agent skill

Check PR Ready

PR 作成前の最終チェックリスト (lint/test/docs/CHANGELOG/未コミット確認)。/precheck の拡張版で、ドキュメント整合性も検証します。

MITAuto-check passedDevelopment

Install Check PR Ready

skills CLI

$ npx skills add ayutaz/piper-plus --skill check-pr-ready -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install ayutaz/piper-plus check-pr-ready --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/ayutaz/piper-plus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/check-pr-ready .claude/skills/check-pr-ready && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "check-pr-ready" agent skill from https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/check-pr-ready into .claude/skills/check-pr-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-pr-ready", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/check-pr-ready

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add ayutaz/piper-plus --skill check-pr-ready -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install ayutaz/piper-plus check-pr-ready --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ayutaz/piper-plus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/check-pr-ready .agents/skills/check-pr-ready && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "check-pr-ready" agent skill from https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/check-pr-ready into .agents/skills/check-pr-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-pr-ready", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add ayutaz/piper-plus --skill check-pr-ready -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install ayutaz/piper-plus check-pr-ready --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ayutaz/piper-plus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/check-pr-ready .cursor/skills/check-pr-ready && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "check-pr-ready" agent skill from https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/check-pr-ready into .cursor/skills/check-pr-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-pr-ready", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/ayutaz/piper-plus.git --path .claude/skills/check-pr-ready

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add ayutaz/piper-plus --skill check-pr-ready -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install ayutaz/piper-plus check-pr-ready --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ayutaz/piper-plus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/check-pr-ready .gemini/skills/check-pr-ready && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "check-pr-ready" agent skill from https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/check-pr-ready into .gemini/skills/check-pr-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-pr-ready", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install ayutaz/piper-plus check-pr-ready

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add ayutaz/piper-plus --skill check-pr-ready -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/ayutaz/piper-plus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/check-pr-ready .github/skills/check-pr-ready && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "check-pr-ready" agent skill from https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/check-pr-ready into .github/skills/check-pr-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-pr-ready", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add ayutaz/piper-plus --skill check-pr-ready -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install ayutaz/piper-plus check-pr-ready --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ayutaz/piper-plus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/check-pr-ready .opencode/skills/check-pr-ready && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "check-pr-ready" agent skill from https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/check-pr-ready into .opencode/skills/check-pr-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-pr-ready", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: check-pr-ready
GitHub stars: 234
Token cost: ~687 tokens
SKILL.md length: 221 words
Files: 1
Skills in repo: 20
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

PR 作成前の最終チェックリスト (lint/test/docs/CHANGELOG/未コミット確認)。/precheck の拡張版で、ドキュメント整合性も検証します。

Works in 5 steps: ブランチと未コミット確認 → コードチェック → ドキュメント整合性チェック → …
Tasks that involve Changelog and release notes
SKILL.md covers 現在の状態, 実行手順 (順番通り、失敗したら停止して報告), 報告フォーマット and 注意
Calls git and gh

What it does

Check PR Ready is an agent skill from ayutaz/piper-plus. PR 作成前の最終チェックリスト (lint/test/docs/CHANGELOG/未コミット確認)。/precheck の拡張版で、ドキュメント整合性も検証します。

Its SKILL.md is about 690 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes and Linting and formatting. It works with Git and Python. The repository describes itself as: Multilingual neural TTS (6 languages: JA/EN/ZH/ES/FR/PT, code supports SV) — C++, C, Rust, Go, Python, npm (WASM). VITS + Prosody, streaming, CUDA/CoreML/DirectML. pip install…. The licence is MIT.

When your agent uses it

Tasks that involve Changelog and release notes
Tasks that involve Linting and formatting

Example prompts

“/check-pr-ready”

Requirements

Python 3
Pre-approved tools (allowed-tools): Bash(uv run *), Bash(cargo *), Bash(dotnet *), Bash(go *), Bash(node *), Bash(npm *), Bash(cmake *), Bash(ctest *), Bash(git *), Bash(gh *), Read, Grep, Glob

Workflow steps

5 steps, taken from the step headings in SKILL.md.

ブランチと未コミット確認
コードチェック
ドキュメント整合性チェック
PR 本文ドラフト
最終判定

What it can do on your machine

Read from SKILL.md and the folder at commit 421d066. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash(uv run *)
- Bash(cargo *)
- Bash(dotnet *)
- Bash(go *)
- Bash(node *)
- Bash(npm *)
- Bash(cmake *)
- Bash(ctest *)
- Bash(git *)
- Bash(gh *)
…and 3 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Check PR Ready loads about 687 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 221 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~25
When it runs · the whole SKILL.md, loaded when a task matches: ~687

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ayutaz/piper-plus at commit 421d066, republished under its MIT licence (© ayutaz). 221 words, ~687 tokens.

Download SKILL.mdSave it as .claude/skills/check-pr-ready/SKILL.md (or your agent's skills folder).

name: check-pr-ready
description: PR 作成前の最終チェックリスト (lint/test/docs/CHANGELOG/未コミット確認)。/precheck の拡張版で、ドキュメント整合性も検証します。
allowed-tools: Bash(uv run *), Bash(cargo *), Bash(dotnet *), Bash(go *), Bash(node *), Bash(npm *), Bash(cmake *), Bash(ctest *), Bash(git *), Bash(gh *), Read, Grep, Glob
argument-hint: [skip-tests]
disable-model-invocation: true

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 が 含まれていない 場合のみ、以下を実行:

/precheck skill を実行 (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 つでも警告/失敗 → 修正項目をリスト化、緑にしてから再実行を促す

報告フォーマット

text

## 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)
修正してから再実行してください。

注意

ユーザーが skip-tests 引数を渡した場合は Phase 2 のみスキップ (緊急修正用)
pytest.ini の --cov に注意: -o addopts="" で上書き
大規模機能 (>100 行) では CLAUDE.md / CHANGELOG / docs/features の更新を必須とする
PR 作成自体は Phase 5 の 提案だけ で、実行はユーザーに任せる

Files

Just SKILL.md in .claude/skills/check-pr-ready of ayutaz/piper-plus.

Open the folder on GitHubat commit 421d066

Compare with similar skills

Check PR Ready next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Check PR Ready compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Check PR Ready this skillayutaz/piper-plus	234	—	~687	Automated safety check: Pass	MIT	today
Saleor Commit Workflowsaleor/saleor	23k	—	~575	Automated safety check: Pass	BSD-3-Clause	today
Commitizencommitizen-tools/commitizen	3.5k	—	~839	Automated safety check: Pass	MIT	2 days ago
pybind11 Release Preparationpybind/pybind11	18k	—	~1.7k	Automated safety check: Pass	Custom licence	today
pybind11 Release Publicationpybind/pybind11	18k	—	~2.5k	Automated safety check: Pass	Custom licence	today
Qt6 QML Code Reviewerx-tools-author/x-tools	1.1k	1 repos	~3.6k	Automated safety check: Pass	BSD-3-Clause	today

Similar skills

Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
23k GitHub stars~575 tokensUpdated today
DevelopmentAuto-check passed
Commitizen
commitizen-tools/commitizen
A skill your agent uses for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the…
3.5k GitHub stars~839 tokensUpdated 2 days ago
DevelopmentAuto-check passed
pybind11 Release Preparation
pybind/pybind11
Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.
18k GitHub stars~1.7k tokensUpdated today
DevelopmentAuto-check passed
pybind11 Release Publication
pybind/pybind11
Walks a maintainer through publishing a pybind11 release after the preparation PR merges, with preflight checks, confirmations before each push and a GitHub release.
18k GitHub stars~2.5k tokensUpdated today
DevelopmentAuto-check passed
Qt6 QML Code Reviewer
x-tools-author/x-tools
Runs a 47-rule deterministic QML linter, then six parallel deep-analysis passes over bindings, layout, loaders, delegates, states, and performance.
1.1k GitHub starsUsed in 1 repo~3.6k tokens
DevelopmentAuto-check passed
PR Push
icebear0828/codex-proxy
Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…
1.8k GitHub stars~2.2k tokensUpdated today
DevelopmentAuto-check: notes

Questions about Check PR Ready

What does Check PR Ready do?

PR 作成前の最終チェックリスト (lint/test/docs/CHANGELOG/未コミット確認)。/precheck の拡張版で、ドキュメント整合性も検証します。. Check PR Ready is an agent skill from ayutaz/piper-plus.

When should I use Check PR Ready?

Check PR Ready fits situations like: tasks that involve Changelog and release notes; tasks that involve Linting and formatting.

How do I install Check PR Ready in Claude Code?

Run `npx skills add ayutaz/piper-plus --skill check-pr-ready -a claude-code`. Or copy the skill folder (.claude/skills/check-pr-ready in ayutaz/piper-plus) into .claude/skills/check-pr-ready in your project. Claude Code loads it when a task matches its description.

How do I install Check PR Ready in Codex?

Run `npx skills add ayutaz/piper-plus --skill check-pr-ready -a codex`. Or copy the skill folder (.claude/skills/check-pr-ready in ayutaz/piper-plus) into .agents/skills/check-pr-ready in your project. Codex loads it when a task matches its description.

Can I use Check PR Ready in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ayutaz/piper-plus --skill check-pr-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/check-pr-ready, .gemini/skills/check-pr-ready, .github/skills/check-pr-ready and .opencode/skills/check-pr-ready in your project.

What does Check PR Ready need to run?

Going by SKILL.md and its folder, Check PR Ready needs the command-line tools its instructions call (git and gh). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash(uv run *), Bash(cargo *), Bash(dotnet *), Bash(go *), Bash(node *), Bash(npm *), Bash(cmake *), Bash(ctest *), Bash(git *), Bash(gh *), Read, Grep, Glob.

Does Check PR Ready access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Check PR Ready safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Check PR Ready use?

Check PR Ready is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Check PR Ready use?

About 687 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Check PR Ready?

Skills that share tags, products or a category with Check PR Ready: Saleor Commit Workflow (saleor/saleor, 23k stars), Commitizen (commitizen-tools/commitizen, 3.5k stars), pybind11 Release Preparation (pybind/pybind11, 18k stars) and pybind11 Release Publication (pybind/pybind11, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Check PR Ready?

ayutaz (a GitHub user) maintains it in ayutaz/piper-plus, which has 234 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 10, 2026.

Source: ayutaz/piper-plus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Check PR Ready

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

PR 作成前 最終チェック

現在の状態

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

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

Phase 2: コードチェック

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

Phase 4: PR 本文ドラフト

Phase 5: 最終判定

報告フォーマット

注意

Files

Compare with similar skills

Similar skills

More from ayutaz/piper-plus

Related

Questions about Check PR Ready

PR 作成前最終チェック