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/issue-fix-design/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/issue-fix-design)<a href="https://agentmods.dev/skills/apokamo/kaji/issue-fix-design"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/issue-fix-design/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/issue-fix-design"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/issue-fix-design.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.00032 | $0.01915 |
| Opus 5 | $0.00016 | $0.00958 |
| Sonnet 5 | $0.00006 | $0.00383 |
| Haiku 4.5 | $0.00003 | $0.00192 |
Grade A, and why
issue-fix-design 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Fix Design
設計レビューで指摘された内容に対し、論理的な妥当性を検討した上で、設計ドキュメントを更新します。
いつ使うか
| タイミング | このスキルを使用 |
|---|---|
/issue-review-design で Changes Requested 後 |
✅ 必須 |
| 一次情報の記載を求められた後 | ✅ 必須 |
ワークフロー内の位置: design → review-design → (fix → verify) → implement
入力
ハーネス経由（コンテキスト変数）
常に注入される変数:
| 変数 | 型 | 説明 |
|---|---|---|
issue_id |
str | 正規化済み Issue ID（GitHub 数値または local ID） |
issue_ref |
str | 人間可読の Issue 参照（GitHub では #<issue_id>、local では bare ID） |
step_id |
str | 現在のステップ ID |
条件付きで注入される変数:
| 変数 | 型 | 条件 | 説明 |
|---|---|---|---|
previous_verdict |
str | resume 指定ステップ |
前ステップの verdict |
cycle_count |
int | サイクル内ステップのみ | 現在のイテレーション番号 |
max_iterations |
int | サイクル内ステップのみ | サイクルの上限回数 |
手動実行（スラッシュコマンド）
$ARGUMENTS = <issue_id>
解決ルール
コンテキスト変数 issue_id が存在すればそちらを使用。
なければ $ARGUMENTS の第1引数を issue_id として使用。
issue_ref はハーネス経由ではプロンプトに自動注入される（prompt.py 側で provider 別に整形）。手動実行時は issue_id から導出する: GitHub 数値 ID なら #<issue_id>、local-* 形式なら bare ID（# を付けない）。
前提知識の読み込み
以下のドキュメントを Read ツールで読み込んでから作業を開始すること。
- テスト規約:
docs/dev/testing-convention.md - コーディング規約:
docs/reference/python/python-style.md- 必要に応じて
docs/reference/python/naming-conventions.md/type-hints.md/docstring-style.md/error-handling.md/logging.mdを追加読込
- 必要に応じて
- 開発ワークフロー:
docs/dev/development_workflow.md
共通ルール
- _shared/report-unrelated-issues.md — 作業中に発見した無関係な問題の報告ルール
実行手順
Step 1: コンテキスト取得
-
_shared/worktree-resolve.md の手順に従い、Worktree の絶対パスを取得。
-
レビュー結果の取得:
- コンテキスト変数
previous_verdictが存在する場合はそれを確認（ハーネス経由） - 存在しない場合は Issue コメントから最新のレビュー結果を取得（手動実行時）
- コンテキスト変数
-
レビュー内容の取得:
kaji issue view [issue_id] --comments最新の「設計レビュー結果」を取得。
-
設計書の現状確認:
cat [worktree_dir]/draft/design/issue-[issue_id]-*.md
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 · 208 lines · 32 tokens per session scan A e2fefc3f9ed7
issue-fix-design is a skill published in the GitHub repository apokamo/kaji (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 1,915 once invoked, about $0.0002 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
software-design-lifecycle-tech-detailed-methodology
Use when an architect must run the detailed-design portion of technical design, preserve the full lifecycle-stage doctrine for detailed design, and define the concrete runtime, project, flow, data, interface, non-functional, security, recovery, hardware, and implementation-plan surfaces needed for execution.
software-design-lifecycle-solution-design-biz-arch-diagramming
A method for designing and reviewing a business-solution architecture: a middle-level view that connects confirmed business problems to a solution before technical implementation is designed.
software-design-lifecycle-tech-overview-system-arch-diagramming
A guide for architects who draw or review system architecture diagrams during overview design. It explains subsystems, outside dependencies, communication links, and system boundaries without going into every technology detail.
creative-claude-design
Design one-off HTML artifacts (landing, deck, prototype).
diagram-drawio
Use when the user requests diagrams, flowcharts, architecture diagrams, ER diagrams, UML / sequence / class diagrams, network topology, ML/DL model figures (Transformer/CNN/LSTM), mind maps, or any visualization. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that…
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…