Borrowing it
Nothing to install: this file belongs to Kewton/CommandMate. 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/Kewton/CommandMate/main/.claude/commands/issue-enhance.mdgit clone --depth 1 https://github.com/Kewton/CommandMateWrote 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/commands/kewton/commandmate/issue-enhance)<a href="https://agentmods.dev/commands/kewton/commandmate/issue-enhance"><img src="https://agentmods.dev/badge/commands/kewton/commandmate/issue-enhance/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/commands/kewton/commandmate/issue-enhance"><img src="https://agentmods.dev/badge/commands/kewton/commandmate/issue-enhance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00020 | $0.04037 |
| Opus 5.5 | $0.00008 | $0.01615 |
| Sonnet 5.5 | $0.00004 | $0.00807 |
| Haiku 4.5 | $0.00002 | $0.00404 |
Grade A, and why
issue-enhance 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 1mo 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 — 502 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue補完コマンド
概要
Issueの記載内容を分析し、不足しているセクションを特定し、ユーザーに質問して情報を収集した上でIssue本文を補完・更新するコマンドです。
目的: タイトルのみ・本文が不十分なIssueを、ユーザーとの対話を通じて実装可能な品質まで引き上げる
使用方法
/issue-enhance [Issue番号]
例:
/issue-enhance 159
実行内容
あなたはIssue補完の専門家です。以下の4フェーズでIssue内容を分析・補完します。
パラメータ
- issue_number: 対象Issue番号（必須）
Phase 1: Issue読み込みと分析
1-1. Issue内容の取得
gh issue view {issue_number} --json title,body,labels
取得したIssue内容を確認し、現状の記載状況を把握する。
1-2. Issue種別の判定
以下の優先順位で種別を判定する：
- ラベルから判定:
feature,bug,documentation,refactorラベルの有無 - タイトルprefixから判定:
feat:,fix:,docs:,refactor:等の接頭辞 - タイトル内容から推測: キーワード（「追加」「修正」「バグ」「不具合」「リファクタ」「ドキュメント」等）
- 判定不能時: AskUserQuestionでユーザーに質問
AskUserQuestion:
question: "Issue #{issue_number} の種別を教えてください"
header: "Issue種別"
options:
- label: "Feature（機能追加）"
description: "新しい機能やUIの追加"
- label: "Bug Fix（バグ修正）"
description: "既存機能の不具合修正"
- label: "Refactor（リファクタリング）"
description: "機能変更なしのコード改善"
- label: "Docs（ドキュメント）"
description: "ドキュメントの追加・更新"
1-3. 必須セクションチェック
種別に応じた必須セクションの充足状況を確認する。
Feature (feat):
| セクション | 必須度 | チェック内容 |
|---|---|---|
| 概要 | 必須 | 何を実現する機能か |
| 背景・課題 | 必須 | なぜこの機能が必要か |
| 提案する解決策 | 必須 | どう実装するか（方針レベル） |
| 実装タスク | 推奨 | 具体的な作業ステップ |
| 受入条件 | 必須 | 完了の判定基準 |
| 影響範囲 | 推奨 | 変更の波及先 |
Bug Fix (fix):
| セクション | 必須度 | チェック内容 |
|---|---|---|
| 概要 | 必須 | どのような不具合か |
| 再現手順 | 必須 | 不具合の再現方法 |
| 期待する動作 | 必須 | 本来どう動作すべきか |
| 実際の動作 | 必須 | 現在どう動作しているか |
| 根本原因の仮説 | 推奨 | 原因の見当 |
| 対策案 | 推奨 | 修正方針 |
| 影響範囲 | 推奨 | 修正の波及先 |
Refactor (refactor):
| セクション | 必須度 | チェック内容 |
|---|---|---|
| 概要 | 必須 | 何をリファクタリングするか |
| 背景・動機 | 必須 | なぜリファクタリングが必要か |
| リファクタリング方針 | 必須 | どのように改善するか |
| 影響範囲 | 推奨 | 変更の波及先 |
| 受入条件 | 必須 | 完了の判定基準 |
Docs (docs):
| セクション | 必須度 | チェック内容 |
|---|---|---|
| 概要 | 必須 | 何のドキュメントか |
| 更新対象ドキュメント | 必須 | どのファイルを変更するか |
| 更新内容 | 必須 | 何を追加・修正するか |
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.
- 1mo ago First seen · 502 lines · 20 tokens per session scan A c28014a52181
issue-enhance is a command published in the GitHub repository Kewton/CommandMate (44 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 4,037 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 commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
aigon-feedback-triage
Run a triage loop for one feedback item with explicit human confirmation before writes.
research-close
Close research - moves to done.
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.