菜单
Close a GitHub issue with a brief comment summarizing the applied fix (inferred from the branch diff if not supplied). Use only on explicit request, e.g. "/close-issue 123".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Rewrite a country rework/additions TASK issue into a clear, mechanic-by-mechanic design brief: study its mockups, inventory the country's existing assets, and reframe each mechanic (goal / real-world idea / starting state / influences / player choices / progression) with AI/tooling hints stripped. Use when asked to reframe, clarify, or rewrite a rework task or roadmap issue, e.g. "/rework-brief JAP 801".
Check a file or the branch diff against the full MD content review checklist (economic, political, visual, military, AI, code) with blocker tags. Use when asked to content-review country content or verify content-guideline compliance before merge.
Scaffold generals, field marshals, and admirals for a country using the MD count formulas and region skill ranges, writing character and recruit_character entries. Use when asked to add leaders, generals, or admirals for a TAG, e.g. "/add-leader NIG".
Wire a country-specific income or expense stream into the MD money system: calculation block, hidden tooltip idea, loc key, and granting effect. Use when asked to add an income or expense stream, e.g. "/additional-income GRE golden_visa income".
Adversarial edge-case hunt over the branch diff or a single file: challenges every change for unhandled scenarios, silent failures, scope/timing/variable traps, and logic gaps rule-based review misses. Use when asked to adversarially review, stress-test, or find edge cases in a change.
Comprehensive pre-merge review of one file or the whole branch diff: dispatches parallel reviewer agents (correctness, adversarial edge cases, performance, simplification, content) and merges findings. Use when asked to audit or fully review a branch or file. Replaces /review-branch.
| name | close-issue |
| description | Close a GitHub issue with a brief comment summarizing the applied fix (inferred from the branch diff if not supplied). Use only on explicit request, e.g. "/close-issue 123". |
| disable-model-invocation | true |
Close a GitHub issue with a brief comment summarizing the fix that was applied.
Supported arguments: an issue number (required), and optionally a short description of the fix. If no description is provided, infer the fix from the current branch's diff against main.
Requested arguments: $ARGUMENTS
Steps:
Parse arguments
Extract the issue number from $ARGUMENTS. If a description is also provided, use it as the comment body. Otherwise, proceed to step 2 to infer one.
Infer the fix summary (skip if a description was provided)
Fetch the issue title for context, then check the current branch diff:
gh issue view <number> --json title,body
git log origin/main..HEAD --oneline
git diff origin/main...HEAD --stat
Write a 1-3 sentence comment covering the root cause and what was changed to fix it. Keep it concise and factual. Do not repeat the issue title back.
Post the comment and close the issue
gh issue close <number> --comment "<summary>"
Report back
Output the issue URL and confirm it was closed.