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/watch-pr/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/watch-pr)<a href="https://agentmods.dev/skills/ayutaz/piper-plus/watch-pr"><img src="https://agentmods.dev/badge/skills/ayutaz/piper-plus/watch-pr.svg" alt="Measured on agentmods" height="20"></a>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.00197 | $0.03247 |
| Opus 5 | $0.00098 | $0.01623 |
| Sonnet 5 | $0.00039 | $0.00649 |
| Haiku 4.5 | $0.00020 | $0.00325 |
Grade A, and why
watch-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 6d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR CI Status Watcher
PR の CI checks を 1 回ポーリングして状態を集計する skill。継続監視は /loop と組み合わせる:
/loop /watch-pr 489 # 5 分間隔で polling、red/green/timeout で通知
/watch-pr # 引数省略時は現在ブランチに紐づく PR を自動検出
引数
$1(任意): PR 番号 (例:489)。省略時はgh pr view --json numberで現在ブランチから自動取得
実行前の確認
- ブランチ: !
git rev-parse --abbrev-ref HEAD - 引数: $ARGUMENTS
手順
フェーズ 1: PR 番号の確定
引数 $1 がない場合、現在ブランチに紐づく PR を取得:
PR_NUM=$(gh pr view --json number --jq '.number' 2>/dev/null)
該当 PR がない場合 (= まだ push していない / PR 未作成) は、その旨をユーザーに報告して停止。
フェーズ 2: CI checks の一括取得
gh pr checks "$PR_NUM" --json name,state,conclusion,link --jq '.[]'
各 check は以下の状態のいずれか:
- state:
QUEUED/IN_PROGRESS/COMPLETED - conclusion (COMPLETED 時のみ):
SUCCESS/FAILURE/CANCELLED/SKIPPED/NEUTRAL/TIMED_OUT/ACTION_REQUIRED
フェーズ 3: 集計とサマリ
以下のテーブルでサマリを表示 (件数は実際の集計値):
## PR #<N> CI Status (<HH:MM:SS>)
| State | Count |
|--------------|-------|
| ✅ Success | <n> |
| ❌ Failure | <n> |
| 🔁 Pending | <n> |
| ⏭️ Skipped | <n> |
| ⚠️ Cancelled | <n> |
Total: <total> checks
判定ルール:
- All green (failure=0, pending=0, cancelled=0): 「全 N checks green、merge 可能状態」
- Red (failure ≥ 1): フェーズ 4 へ
- Pending (queued/in_progress ≥ 1): 「N checks がまだ走行中、再度 polling を推奨」
- Suspicious skip (cancelled+skipped が 3 件以上連続): silent skip の可能性を警告 (PR #419 事例)
フェーズ 4: 失敗 job の分析 (failure ≥ 1 時のみ)
各失敗 job について:
- job 名と link を表示
gh run view <run-id> --log-failedで失敗 step のログを fetch (最大 100 行)- ログを以下の pattern で分類:
- Format drift:
ruffcargo fmtgofmtdotnet formatclippy系のエラー → ローカルpre-commit run --all-filesで修復可能 - Test fail:
FAILEDassertpanickedexpected系 → どのテストかを抽出 - Build error:
error[E0cannot findundefined reference系 → コンパイルエラー - Flake:
timeoutnetworkconnection resetrate limit系 → 一過性、retry 推奨 - Contract drift:
MISMATCHOUT OF SYNCbyte-for-byte系 → 該当check-*skill を案内
- Format drift:
- 分類別に推奨アクションを提示
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.
- 6d ago First seen · 231 lines · 197 tokens per session scan A 1dee68909231
watch-pr is a skill published in the GitHub repository ayutaz/piper-plus (204 stars, last pushed 4d ago), licensed MIT. It adds 197 tokens to every session and 3,247 once invoked, about $0.0010 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.
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…
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.