菜单
List GitHub issues, let the user pick one, and download all content including images so an agent can work on it. Use this when the user wants to browse, review, or select issues to work on.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | read-issues |
| description | List GitHub issues, let the user pick one, and download all content including images so an agent can work on it. Use this when the user wants to browse, review, or select issues to work on. |
| disable-model-invocation | true |
| argument-hint | [optional: issue number, label filter, or search query] |
Browse, filter, and select GitHub issues, then download all content and images so an agent can fully understand and work on the selected issue.
If a specific issue number is provided in $ARGUMENTS, skip to Step 2.
If a search query or label filter is provided, use it:
# By label
gh issue list --label "bug" --state open
# By search
gh issue list --search "QUERY" --state open
# All open issues
gh issue list --state open --limit 30
If no filter is provided, list all open issues:
gh issue list --state open --limit 30
Display the issues in a clear format showing:
$ARGUMENTS contains a specific issue number, use that directlyOnce an issue is selected, fetch everything:
# Get full issue details including body
gh issue view ISSUE_NUMBER
# Get all comments
gh issue view ISSUE_NUMBER --comments
# Get issue metadata as JSON for structured parsing
gh issue view ISSUE_NUMBER --json title,body,labels,assignees,comments,state,milestone,createdAt,updatedAt,author
 — Markdown imageshttps://github.com/user-attachments/... — GitHub uploaded imageshttps://user-images.githubusercontent.com/... — Legacy GitHub imagescurl or Invoke-WebRequest$env:TEMP/gh-issues/ISSUE_NUMBER/Provide a comprehensive summary including:
## Issue #NUMBER: TITLE
**State:** open/closed
**Labels:** label1, label2
**Assignee:** @username
**Created:** date
**Author:** @username
### Description
[Full issue body]
### Images
[Display all downloaded images]
### Comments (N total)
[All comments with authors and dates]
### Key Requirements
- [Extracted actionable items from the description]
- [Any acceptance criteria mentioned]
### Related Files (if mentioned)
- [Any file paths or code references from the issue]
After presenting the issue, ask the user:
/developer-agent NUMBER, or /implementation-loop NUMBER to drive it through Dev+QA to merged)gh CLI for all GitHub operationsRelocate a live session to another cc-director slot or Director - approval-gated handover through the GATEWAY, the seed identifies itself as a moved session, the TARGET keeps the source's original name, the source is renamed "[MOVED]" and put on hold so the user can close it. Triggers on "/move-session", "move session", "migrate session", "transfer session".
INTERNAL reference, NOT shipped with the installer. The in-repo expert on every coding-agent CLI CC Director can run (Claude Code, Codex, Gemini, OpenCode, Grok, Copilot, Cursor, Pi). Knows each agent's command line, config files, context-injection points, lifecycle hooks and events, SDK/API/server mode, transcript format, session semantics, and how CC Director drives it. Triggers on "agent-expert", "agent expert", "how does <agent> inject context", "<agent> hooks", "<agent> events", "<agent> CLI reference", "which agents support X", "agent capability matrix".
How a mission is RUN in this repository - the Architect, the Manager, the Workers, and the independent Inspector, plus the four standing laws (ask up front then run alone, and NEVER guess - bring the owner in when something is genuinely undecidable; the mission branch holds the work and only the Architect lands it on main; a different agent family inspects before anything reaches main; merged to origin/main is the only done). Read this BEFORE starting or seeding any mission, and before writing any mission brief. Triggers on "/mission", "start a mission", "run a mission", "seed an architect", "write a mission brief", "mission brief", "who merges", "mission roles".
DevThrottle - "Mission Control for Claude Code". A desktop app (binary cc-director.exe) that runs and supervises multiple Claude Code sessions and ships cc-* CLI tools on PATH. Agents drive the fleet through the cc-devthrottle command, not by calling the Director over HTTP. Triggers on "/dev-throttle", "/devthrottle", "/cc-director", "what cc tools", "list tools", "available tools", "devthrottle api", "session manager", "mission control".
Talk to other DevThrottle sessions across the fleet. Use when you want to list running sessions, rename this session, message another session, ask another session a question and get its answer, or open a new session - from inside a session. Triggers on "/fleet-comms", "message another session", "talk to another session", "ask another session", "rename this session", "rename session", "list sessions", "what sessions are running", "open a session", "spawn a session", "cc-devthrottle", "fleet messaging", "session intercommunication".
Guided run-book for cutting a DevThrottle release - assemble the changes, write the release notes, coordinate the internal docs site, cut the tag, and announce it. Triggers on "/release-manager", "cut a release", "prepare a release", "ship a release", "do the release".