piper-plus: Skill for Claude Code

.claude/skills/check-review-backlog/SKILL.md

check-review-backlog is a skill for Claude Code from ayutaz/piper-plus. It costs 118 tokens per session (1,815 once invoked), scanned A, original, MIT.

A read-only checker for open GitHub pull requests that finds review conversations no one has resolved. It can check one pull request immediately or scan all open pull requests for older items.

In plain words
What is it for?
Use it after creating a pull request or for a regular review-backlog check. You can filter results by pull request, waiting time, or reviewer.
Why use it?
It helps prevent review comments from being forgotten. It also shows which unresolved conversations have been waiting longer than a chosen number of days.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

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 →

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-review-backlog/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-review-backlog

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/ayutaz/piper-plus/check-review-backlog"><img src="https://agentmods.dev/badge/skills/ayutaz/piper-plus/check-review-backlog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 118 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,815 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.00118 $0.01815
Opus 5 $0.00059 $0.00907
Sonnet 5 $0.00024 $0.00363
Haiku 4.5 $0.00012 $0.00181

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

Security

Grade A, and why

check-review-backlog 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 10d 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-review-backlog/SKILL.md · 164 lines

How it starts

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

Unresolved Review Backlog Monitor

全 open PR を走査して、未解決 (isResolved=false) の review thread のうち N 日以上経過しているものを backlog として集計する。レビュー対応漏れの早期警告が目的。

引数

  • --pr <N> (任意): 単一 PR の review 即時確認モード。 経過日数フィルタを無視し、 全未解決 thread を表示。 /create-pr skill から PR 作成直後に自動 chain される (例: /check-review-backlog --pr 496)
  • --days N (任意): 経過日数の閾値 (デフォルト: 7 日)。 --pr 指定時は無視
  • --author <login> (任意): 特定 reviewer (例: copilot-pull-request-reviewer) のコメントに絞る

実行前の確認

  • 現在時刻 (UTC): !date -u +"%Y-%m-%dT%H:%M:%SZ"
  • 引数: $ARGUMENTS

手順

フェーズ 0: モード判定

$ARGUMENTS を解析:

  • --pr <N> を含む: 単一 PR モード (PR 作成直後の auto chain 用)。 フェーズ 1 を skip、 フェーズ 2 を該当 PR 1 件で実行、 フェーズ 3 (日数フィルタ) を skip、 フェーズ 4 で「PR #N の未解決 thread 全件」レポート
  • それ以外: backlog 監視モード (週次運用)。 全 open PR を走査

フェーズ 1: Open PR 一覧取得 (backlog モードのみ)

gh pr list --state open --json number,title,createdAt,updatedAt --limit 50

各 open PR について、フェーズ 2 を実行する。

フェーズ 2: 未解決 thread の集計

各 PR について、GraphQL で未解決 review thread + 最初のコメントを取得:

gh api graphql -f query='
query($pr: Int!) {
  repository(owner: "ayutaz", name: "piper-plus") {
    pullRequest(number: $pr) {
      title
      reviewThreads(first: 50) {
        nodes {
          id
          isResolved
          comments(first: 1) {
            nodes {
              databaseId
              path
              line
              body
              createdAt
              author { login }
              url
            }
          }
        }
      }
    }
  }
}' -F pr=<PR_NUMBER> --jq '.data.repository.pullRequest | {
  title,
  unresolved: [.reviewThreads.nodes[] | select(.isResolved == false) | .comments.nodes[0]]
}'

フェーズ 3: 経過日数フィルタリング

各 thread の createdAt (ISO8601) と現在時刻を比較し、days_old >= --days のものを抽出:

# 概念 pseudocode (実際は bash + jq + date で実装)
from datetime import datetime, timezone
now = datetime.now(timezone.utc)
threshold_days = int(args.days or 7)
for thread in unresolved_threads:
    created = datetime.fromisoformat(thread["createdAt"].replace("Z", "+00:00"))
    days_old = (now - created).days
    if days_old >= threshold_days:
        backlog.append({**thread, "days_old": days_old})

Read the full file on GitHub · 164 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. 10d ago First seen · 164 lines · 118 tokens per session scan A 77c084770aa0

Subscribe to this mod's changes

check-review-backlog is a skill published in the GitHub repository ayutaz/piper-plus (204 stars, last pushed 8d ago), licensed MIT. It adds 118 tokens to every session and 1,815 once invoked, about $0.0006 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.

Related

Other skills, from other repositories

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, and exact-head validation evidence. Use for contributor self-review before marking a PR ready, or when deciding whether a community PR is…

NVIDIA/TensorRT-Model-Connect · 98 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

review-implement-phase

Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.

prisma/orm · 38 tokens