菜单
Check GitHub issues and tickets for the current repo. List open issues, view details, filter by label, or search. Use when the user asks about issues, tickets, bugs, or backlog.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Session closing checklist for Git state, documentation, handoff files, and Munin memory. Use when the user invokes /close or asks to wrap up a session, including work that touched multiple repositories.
Resolve a batch of GitHub tickets via parallel headless Claude Code sessions — one isolated git worktree per ticket, gated permissions, triple review (Codex + local-model first-pass + orchestrator comment), interrupt-resume, and merge orchestration. Use when the user wants many well-scoped tickets solved autonomously across one or more repos.
Run an adversarial debate with Claude to stress-test a draft, plan, research claim, or design decision. Use when Codex needs structured cross-model critique before finalizing a consequential decision, architecture, protocol, research claim, security assessment, or product priority.
Run an adversarial debate with a cross-model reviewer (Codex or Antigravity/agy) to stress-test a draft, plan, research claim, or design decision. Use this whenever you need structured critique before finalizing decisions.
Run a cross-model PR review using Codex CLI. Invokes Codex headless to review the current branch diff, then reads findings and fixes issues or reports to user.
Sweep the Munin signals/friction corpus (report_friction self-reports), group recurring failures, and file consolidated GitHub issues routed to their owning repos + the Grimnir Roadmap board. Use when the user wants to triage accumulated friction, turn friction signals into tickets, or asks "what friction have we collected / let's file tickets for it".
| name | issues |
| description | Check GitHub issues and tickets for the current repo. List open issues, view details, filter by label, or search. Use when the user asks about issues, tickets, bugs, or backlog. |
Check open issues and tickets for the current repo using the GitHub CLI.
/issues — list all open issues/issues <number> — view a specific issue by number/issues <label> — filter by label (e.g., bug, security, enhancement)/issues closed — show recently closed issues/issues search <query> — search issues by keywordUse the git remote to determine the owner/repo:
gh repo view --json nameWithOwner -q '.nameWithOwner'
If this fails, tell the user they're not in a GitHub repo.
List open issues (default):
gh issue list --repo <owner/repo> --state open
View a specific issue:
gh issue view <number> --repo <owner/repo>
Filter by label:
gh issue list --repo <owner/repo> --state open --label "<label>"
Show recently closed:
gh issue list --repo <owner/repo> --state closed --limit 10
Search by keyword:
gh issue list --repo <owner/repo> --state open --search "<query>"
For issue lists: Group by label and show a compact summary:
**Bugs (2):**
- #1 — Task status tags never flip from pending to running
- #2 — mDNS flaky
**Enhancements (1):**
- #3 — Phase 5: Sensitivity classification
If an issue has no labels, group it under Other.
For single issue view: Show title, status, labels, body, and any comments. If the issue references code, note the relevant files.
After presenting, briefly suggest relevant actions:
Don't be verbose about it — one line is enough.
--repo — don't assume gh will infer correctly from the working directory in all cases.