菜单
Show open issue trees, blockers, linked pull requests, announcements, and issues waiting on evidence from GitHub's native coordination state
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit GitHub issues against repository state or evidence-backed acceptance criteria, then reconcile confirmed issue changes through one complete Issue Plan.
File or reconcile one or more GitHub issues from Work Type templates through one complete Issue Plan, with clarifying questions, native parent and blocker routing, evidence-backed acceptance criteria, and agent attribution. Use when the user says 'file an issue', 'open a bug', 'log a feature', 'track this task', 'turn these findings into issues', or runs a /github-coordination:file-*-issue or /github-coordination:to-issues command.
Create or update a repo-local announcement through one complete Issue Plan, preserving bot attribution and optionally pinning the resulting issue. Use when the user says 'post an announcement', 'announce the release', 'update the pinned notice', or runs /github-coordination:create-announcement or /github-coordination:update-announcement.
Turn a supplied report, audit, or backlog slice into one coordinated issue plan with native parent and blocker relationships
Audit GitHub issues against repository state or evidence-backed acceptance criteria, then reconcile confirmed issue changes through one complete Issue Plan.
File or reconcile one or more GitHub issues from Work Type templates through one complete Issue Plan, with clarifying questions, native parent and blocker routing, evidence-backed acceptance criteria, and agent attribution. Use when the user says 'file an issue', 'open a bug', 'log a feature', 'track this task', 'turn these findings into issues', or runs a /github-coordination:file-*-issue or /github-coordination:to-issues command.
| name | show-repo-status |
| description | Show open issue trees, blockers, linked pull requests, announcements, and issues waiting on evidence from GitHub's native coordination state |
| user-invocable | true |
Treat the user's invocation text after show-repo-status as $ARGUMENTS.
Render one read-only summary from the GitHub Coordination Ledger. Every line must trace to a GitHub read; this command never writes or invents state.
gh repo view --json nameWithOwner -q .nameWithOwner
gh issue list --state open --label parent --json number,title
gh issue list --state open --limit 200 --json number,title,body,labels
gh pr list --state open --json number,title,headRefName,body
gh issue list --state open --label announcement --json number,title
For each open parent and issue, read native relationships:
gh api --paginate repos/OWNER/REPO/issues/NUMBER/sub_issues
gh api --paginate repos/OWNER/REPO/issues/NUMBER/dependencies/blocked_by
Bound network calls so an unavailable remote fails clearly instead of leaving the view waiting indefinitely.
sub_issues results. Issue-body
headings and task lists are content, never relationship evidence.blocked_by result contains an
open blocker. Include closed blockers only when they explain a recent state
transition.Evidence: slot.REPO STATUS — <owner/repo>
PARENT ISSUES (open)
#12 Checkout rewrite
├─ #13 Cart persistence open · linked PR #40
├─ #14 Payment retry closed ✓
└─ #15 Confirmation email open · waiting on evidence (2 of 3 AC)
BLOCKED ISSUES (open)
#18 Refund settlement — blocked by #17 Payment provider contract
LINKED PRS (open)
#40 Persist cart → closes #13
ANNOUNCEMENTS (open)
#22 v0.9 release notes (pinned)
WAITING ON EVIDENCE
#15 Confirmation email — 2 of 3 criteria have no evidence
UNLINKED PRS (open)
#41 Dependency refresh
Show only populated sections. An empty repository prints one line saying there are no open coordination items.
This view is read-only. Filing and issue reconciliation go through one Issue
Plan. Pull requests remain in /open-pull-request; git sync and worktrees remain
in github-workflow.