Borrowing it
Nothing to install: this file belongs to apokamo/kaji. 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/apokamo/kaji/main/.claude/skills/review/SKILL.mdgit clone --depth 1 https://github.com/apokamo/kajiWrote 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/apokamo/kaji/review)<a href="https://agentmods.dev/skills/apokamo/kaji/review"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/review/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.
<a href="https://agentmods.dev/skills/apokamo/kaji/review"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/review.svg" alt="Reviewed on agentmods" width="80" 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.00080 | $0.03461 |
| Opus 5 | $0.00040 | $0.01731 |
| Sonnet 5 | $0.00016 | $0.00692 |
| Haiku 4.5 | $0.00008 | $0.00346 |
Grade A, and why
review 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 9d 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review
PR に対する 初回コードレビュー を実施するスキル。
設計書整合 / コード品質 / テスト証跡 / docs 更新を観点に評価し、kaji pr review で正式な
Approve / Changes Requested を投稿する。
重要: このスキルは 新規レビュー 専用。修正確認（
/pr-fix後の収束確認）は/pr-verifyを使うこと。両者を混同するとレビューサイクルが収束しなくなる。
いつ使うか
| タイミング | このスキル |
|---|---|
PR 作成直後の初回レビュー（単体起動 / review-poll の BACK_FALLBACK 後の fallback） |
✅ 必須 |
/pr-fix 後の修正確認 |
❌ /pr-verify を使う |
provider.type='github' で codex auto-review が走る環境 |
⚠️ workflow からは review-poll 経由で fallback 用途のみ |
provider.type='github' で codex auto-review が走らない環境（クレジット不足等） |
✅ review-poll → BACK_FALLBACK → 本 skill |
provider.type='local' 配下 |
❌ Step 0 で ABORT。代替は /issue-review-code |
ワークフロー内の位置: i-pr → [PR 作成] → review → (pr-fix → pr-verify) → close
入力
ハーネス経由（コンテキスト変数）
| 変数 | 型 | 説明 |
|---|---|---|
issue_id |
str | 正規化済み Issue ID |
issue_ref |
str | 人間可読の Issue 参照 |
provider_type |
str | github / local のいずれか。Step 0 のガード判定に使用 |
step_id |
str | 現在のステップ ID |
手動実行（スラッシュコマンド）
$ARGUMENTS = <issue_id>
解決ルール
コンテキスト変数 issue_id が存在すればそちらを使用。なければ $ARGUMENTS の第 1 引数を
issue_id として使用。pr_id は Step 1 で kaji pr list --search から逆引きする
（pr-verify と同じ規約）。
前提知識の読み込み
以下のドキュメントを Read ツールで読み込んでから作業を開始すること。
- 開発ワークフロー:
docs/dev/development_workflow.md - テスト規約:
docs/dev/testing-convention.md - Python スタイル:
docs/reference/python/python-style.md
共通ルール
- _shared/report-unrelated-issues.md — 作業中に発見した無関係な問題の報告ルール
必須情報源 / 任意情報源
初回レビュー判定（Approve / Changes Requested）を出すために 必ず読まなければならない情報源:
| Step | 情報源 | 必須/任意 |
|---|---|---|
| Step 3a | kaji pr view [pr_id] — PR タイトル / 説明 / 状態 / linked Issue |
必須 |
| Step 3b | git diff [git_remote]/[default_branch]...HEAD — レビュー対象の差分本体 |
必須 |
| Step 3c | kaji pr review-comments [pr_id] — 既存 inline 指摘（重複指摘回避） |
必須 |
| Step 3d | kaji pr reviews [pr_id] — 過去の Approve / Changes Requested 履歴 |
任意 |
| Step 3e | kaji pr view [pr_id] --comments — 非 inline の議論経緯 |
任意 |
| Step 4 | make check — 品質ゲート（失敗時は Changes Requested 必至） |
必須 |
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.
- 9d ago First seen · 335 lines · 80 tokens per session scan A 81fd9d5e8a22
review is a skill published in the GitHub repository apokamo/kaji (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 80 tokens to every session and 3,461 once invoked, about $0.0004 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
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
merge-queue
Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
review-open-pull-requests
List and analyze all open pull requests across GitHub repositories. Shows review status, CI/CD check results, age, and reviewers. Use when triaging PRs, checking team velocity, or identifying stale reviews that need attention.
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy. Use when PR preparation or commit strategy is needed.
software-development-norms
Use when writing, reviewing, or refactoring code in any language to apply industrial-grade development norms abstracted from the Alibaba Java Development Handbook. Covers naming, type safety, exceptions, logging, concurrency, databases, project structure, testing, and security with language-agnostic principles and…