菜单
Discusses and refines an existing GitHub issue through an iterative dialogue, optionally spawning specialist agents to deepen understanding, then saves a structured markdown issue file and, on confirmation, kicks off planning on a committed branch. Usage: /discuss-issue #19
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Monitors a given PR for merge/close/approval/new owner comments, blocking until one of those occurs, then reports the outcome. Tracks each owner comment's open/addressed lifecycle with :eyes:/:+1: reactions on the comment itself, but leaves deciding how to address a comment to the caller. Usage: /auto-monitor-pr <pr_number>
Autonomously runs the full pipeline (new issue → plan → fix → monitor) for a queue of issue IDs, one at a time, forever — waiting for new IDs to be pushed onto the queue whenever it runs dry — with no user interaction except when a PR is closed without merging. Usage: /auto-fix-all <id1> <id2> ...
Autonomously implements a planned issue with no user interaction. Discovers the specialist agents involved in the plan, dispatches them in parallel, reviews and re-dispatches until correct, then opens or marks ready a pull request. Usage: /auto-fix-issue <id> or /auto-fix-issue #<id>
Resolves the PR for an issue's currently checked-out branch, then monitors it for merge/close/approval/new owner comments, blocking until one of those occurs. Used by auto-fix-all. Usage: /auto-monitor-issue-pr <id>
Configures CLAUDE.md and .github/copilot-instructions.md for a project, creating or updating them to point to a shared AGENTS.md file. Handles multiple scenarios depending on which files already exist. Usage: /init-claude
Creates a implementation plan for a given issue. Reads the issue file, analyzes the codebase, asks clarifying questions, and writes a structured plan in the plans folder. Usage: /plan-issue 99 or /plan-issue #99
| name | discuss-issue |
| description | Discusses and refines an existing GitHub issue through an iterative dialogue, optionally spawning specialist agents to deepen understanding, then saves a structured markdown issue file and, on confirmation, kicks off planning on a committed branch. Usage: /discuss-issue #19 |
You are acting as the architect, helping the user define and refine an existing GitHub issue through interactive dialogue for the current project. You handle the issue evaluation yourself and, when the issue needs deeper context than the description alone provides, spawn other specialist agents to investigate before asking the user questions. This skill only handles issues pre-populated from GitHub — a real, existing GitHub issue number is required. Follow the steps below precisely and in order.
The issues folder is always docs/agents/issues.
Read steps/extract_id_and_name.md and follow the instructions there.
Read steps/discuss_and_save.md and follow the instructions there.
