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-start/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-start)<a href="https://agentmods.dev/skills/apokamo/kaji/issue-start"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/issue-start/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-start"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/issue-start.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.00037 | $0.01750 |
| Opus 5.5 | $0.00015 | $0.00700 |
| Sonnet 5.5 | $0.00007 | $0.00350 |
| Haiku 4.5 | $0.00004 | $0.00175 |
Grade A, and why
issue-start 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 11d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Start
イシュー対応を開始するためのworktreeをセットアップし、Issue本文にメタ情報を追記します。
いつ使うか
| タイミング | このスキルを使用 |
|---|---|
| コード/ドキュメント変更を伴うイシュー着手 | ✅ 必須 |
| 設計のみ（ファイル変更なし） | ⚠️ 任意 |
| 調査・リサーチのみ | ❌ 不要 |
重要: PRを作成する際やイシュー対応でコミットが必要な場合、git branch ではなくこのスキルを使用してください。
引数
$ARGUMENTS = <issue_id>
issue_id(必須): Issue番号 (例: 247 /gh:153)
第 2 引数は 廃止 されました。ブランチ prefix は
kaji issue context が返す branch_prefix（type:* ラベル → chore fallback の
優先順）から自動決定します。
命名規則
kaji issue context <issue_id> の出力（provider.resolve_issue_context() が正本）から
取得する branch_name / worktree_dir をそのまま使います。
- ブランチ名:
<branch_prefix>/<issue_id>(例:fix/247) - ディレクトリ:
<repo_root>/../kaji-<branch_prefix>-<issue_id>(例:../kaji-fix-247)
実行手順
Step 0: 引数の検査
$ARGUMENTS から issue_id を取得してください。第 2 引数（旧 prefix）が
渡された場合は ABORT verdict を出して停止し、廃止アナウンスをユーザに返してください
（type:* ラベルからの自動導出に一本化されているため）。
Step 1: context 正本の取得
system jq バイナリ依存を持ち込まないため、kaji issue context の -q (Python jq) を使う:
PREFIX=$(kaji issue context [issue_id] -q '.branch_prefix')
BRANCH=$(kaji issue context [issue_id] -q '.branch_name')
WT=$(kaji issue context [issue_id] -q '.worktree_dir')
worktree_dir は絶対パスで返ります。以降の手順では上記 3 変数を使います。
Step 2: ブランチとWorktreeの作成
メインリポジトリのルートから実行:
MAIN_REPO=$(git rev-parse --show-toplevel)
git worktree add -b "$BRANCH" "$WT" main
Step 2.5: venv シンボリックリンク作成
main プロジェクトの .venv へのシンボリックリンクを作成:
ln -s "$MAIN_REPO/.venv" "$WT/.venv"
これにより make check が即座に実行可能になります。
Step 2.6: config overlay (.kaji/config.local.toml) シンボリックリンク作成
.kaji/config.local.toml は gitignored のため git worktree add では worktree に転写されない。
overlay 不在の worktree では kaji CLI が .kaji/config.toml だけで動き、main 側で上書きした
マシン固有設定（[execution] 等）が worktree 配下の実行に反映されない。
main の overlay が存在する場合のみ、worktree の .kaji/ にシンボリックリンクで共有する:
if [ -f "$MAIN_REPO/.kaji/config.local.toml" ]; then
ln -sf "$MAIN_REPO/.kaji/config.local.toml" "$WT/.kaji/config.local.toml"
fi
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.
- 11d ago Changed · -3 lines 1414bf1e38aa
- 1mo ago First seen · 174 lines · 37 tokens per session scan A 43d695c6f74d
issue-start is a skill published in the GitHub repository apokamo/kaji (15 stars, last pushed 5d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,750 once invoked, about $0.0001 per session on Opus 5.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
superpowers-finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.