القائمة
Post a reply comment to a GitHub issue. Use when the user wants to respond to an issue, acknowledge a bug report, or share a fix reference with the reporter.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when showing a Web board for a Markdown-only Agent Team Mission without a Mexus server.
Use when opening a RoundTable proposal in the active Markdown-backed Agent Team Mission.
Use when executing the next tasks from a Markdown-backed Agent Team kanban with Claude Code or Codex background Agents.
Use when starting or continuing a Markdown-only Agent Team Mission with Claude Code or Codex background Agents and no Mexus server.
Use when summarizing a Markdown-only Agent Team Mission from local files.
Use when stopping the local Web board for a Markdown-only Agent Team Mission.
| name | gh-issue-reply |
| description | Post a reply comment to a GitHub issue. Use when the user wants to respond to an issue, acknowledge a bug report, or share a fix reference with the reporter. |
| user-invocable | true |
| allowed-tools | ["Bash(gh issue view*)","Bash(gh issue comment*)","Bash(gh repo view*)","Bash(git log*)","Bash(git remote*)","Read"] |
Draft and post a reply to the specified issue. Arguments passed: $ARGUMENTS.
Parse $ARGUMENTS to find:
#N, N, or a full URL https://github.com/OWNER/REPO/issues/N中文 / zh / cn → Chinese; en / english → English; default Chinese unless the issue body is Englishcommit:<sha> or a short sha — include it in the replyIf the issue number cannot be determined, ask the user.
Fetch context: gh issue view <N> --repo <owner/repo> --json title,body,author,state,labels,comments. Read the body and recent comments so the reply is grounded in what was actually reported.
Correlate with recent work (only if relevant):
git log --oneline -10 for any commit that plausibly fixes the issue. Only cite it if the connection is clear — do not speculate.Draft the reply in the requested language. Keep it focused:
<sha>" or "will land in next release" line when applicable.Confirm before posting: show the drafted reply to the user and ask for approval unless they explicitly said "just post it" / "直接发".
Post: gh issue comment <N> --repo <owner/repo> --body "$(cat <<'EOF'\n<body>\nEOF\n)". Use HEREDOC for correct formatting.
Return the comment URL printed by gh.
gh auth login.