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/pr-fix/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/pr-fix)<a href="https://agentmods.dev/skills/apokamo/kaji/pr-fix"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/pr-fix.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.00026 | $0.02696 |
| Opus 5 | $0.00013 | $0.01348 |
| Sonnet 5 | $0.00005 | $0.00539 |
| Haiku 4.5 | $0.00003 | $0.00270 |
Grade A, and why
pr-fix 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Fix
PR 上のコードレビューコメントに基づき、修正対応を行う。 指摘を盲目的に受け入れるのではなく、技術的な妥当性を検討し、修正と反論を使い分ける。
いつ使うか
| タイミング | このスキルを使用 |
|---|---|
| PR にレビューコメント（Changes Requested 等）が付いた後 | ✅ 必須 |
| PR 作成前（Issue ワークフロー内のレビュー） | ❌ /issue-fix-code を使用 |
provider.type='github' 配下 |
✅ 受理（gh CLI 経由） |
provider.type='local' 配下 |
❌ Step 0 で ABORT。代替は /issue-review-code 等 |
ワークフロー内の位置: i-pr → [PR review] → (pr-fix → pr-verify) → close
引数
$ARGUMENTS = <issue_id>
- Issue 番号を受け付ける（関連 PR を自動解決する）
コンテキスト変数
| 変数 | 型 | 説明 |
|---|---|---|
issue_id |
str | 正規化済み Issue ID（GitHub 数値、または local-*） |
issue_ref |
str | 人間可読の Issue 参照（GitHub では #<issue_id>、local では bare ID） |
provider_type |
str | github / local のいずれか。Step 0 のガード判定に使用 |
git_remote |
str | git remote 名（provider.<type>.git_remote config から解決。未指定時のフォールバックは kaji_harness/config.py 定義）。Step 4 の git push 引数に使用 |
解決ルール
コンテキスト変数 issue_id が存在すればそちらを使用。
なければ $ARGUMENTS の第1引数を issue_id として使用。
issue_ref はハーネス経由ではプロンプトに自動注入される（prompt.py 側で provider 別に整形）。手動実行時は issue_id から導出する: GitHub 数値 ID なら #<issue_id>、local-* 形式なら bare ID（# を付けない）。
pr_id / pr_ref はハーネス経由ではプロンプトに自動注入される（runner.py の _resolve_pr_context_safe が GitHubProvider.resolve_pr_context() 経由でブランチから PR を逆引きして展開する）。手動実行時、および auto-resolve が失敗した（branch 未 push / PR 未作成）場合は Step 1 で fallback として kaji pr list --head から取得する。pr_ref は gh:<pr_id> 形式で組み立てる（kaji_harness/providers/models.py PRContext 準拠）。
前提知識の読み込み
変更対象に応じて、以下のドキュメントを Read ツールで読み込んでから作業を開始すること。
- テスト規約:
docs/dev/testing-convention.md - コーディング規約:
docs/reference/python/python-style.md（型ヒント、docstring 等） - エラーハンドリング:
docs/reference/python/error-handling.md
共通ルール
- _shared/report-unrelated-issues.md — 作業中に発見した無関係な問題の報告ルール
実行手順
Step 0: provider check
本 Skill は forge provider 専用。最初に provider_type を解決し、
github 以外なら 以降のステップに進まず ABORT verdict を出力して終了 する。
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 · 260 lines · 26 tokens per session scan A 83c5eec8825c
pr-fix is a skill published in the GitHub repository apokamo/kaji (12 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 2,696 once invoked, about $0.0001 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…