菜单
EPIC 単位で sub-issue / blocked-by / Project status を棚卸しし、進捗・滞留・次に着手すべき Task をレポートするワークフロー。Use when the user asks to "review progress", "EPIC の進捗を確認", "棚卸し", "what's next", "次に何をやる", "blockers を確認", or wants a status snapshot of an EPIC.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the user asks to "lint AI assistant config", "check AGENTS.md", "validate SKILL.md", "agnix lint", or wants to detect and fix best-practice violations in Claude Code / agent configuration files.
This skill is the mandatory reference for all Claude Code hook creation. Use cc-hooks-ts for every hook. This skill should be used when the user asks to "create a hook", "add a hook", "write a hook", "implement a hook", "rewrite hooks in TypeScript", "use cc-hooks-ts", or needs to build any Claude Code hook — cc-hooks-ts is always required regardless of whether explicitly mentioned.
Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.
This skill should be used when the user asks to "handoff from CCS", "Claude Codeの作業を引き継ぐ", "rate limit handoff", "context overflow", or wants to resume interrupted work from another CCS profile session.
This skill should be used when the user asks for "code review", "レビューして", "review this diff", "実装をレビュー", or wants rigorous review of recently created artifacts.
Direct utility reference for code-review PR scripts. Documents unresolved-thread, comment, CI-status, and CI-log helpers used by higher-level PR workflows.
| name | gh-projects:review-progress |
| description | EPIC 単位で sub-issue / blocked-by / Project status を棚卸しし、進捗・滞留・次に着手すべき Task をレポートするワークフロー。Use when the user asks to "review progress", "EPIC の進捗を確認", "棚卸し", "what's next", "次に何をやる", "blockers を確認", or wants a status snapshot of an EPIC. |
EPIC 1つを起点に、配下の Story / Task / 依存関係 / Project Status を集計し、現状と次アクションを提示する。
<owner>/<repo> と <epic#>../../scripts/gh-project.ts deps:show <owner>/<repo> <epic#>
得られる情報:
subIssuesSummary）各 Story について再帰的に集計:
../../scripts/gh-project.ts deps:show <owner>/<repo> <story#>
Task の open/closed と blocked-by を収集する。
Project Status を見たい場合:
../../scripts/gh-project.ts item:list <owner> <project#>
Issue 番号で突き合わせて Status / Iteration を付与する（CLI 出力をパースする）。
各 open Issue を以下のバケットに分類:
検証 Story は close されず Need Review で止まる（→ epic-story-task skill）。進捗は Need Review 以降を完了相当として数える。"長期間" は文脈依存。
ユーザーに以下を返す:
## EPIC #<n>: <title>
進捗: <needReview+closed>/<total> Story 完了相当 (<percent>%) ／ うち closed <closed>
### Ready to start (X)
- #<n> <title> — assignee: <user|->
### In Progress (X)
- #<n> <title> — assignee: <user|->, status updated <days> ago
### Blocked (X)
- #<n> <title> — blocked by #<m> (<m-title>, status: <status>)
### Need Review (X)
- #<n> <title> — 作業・確認は完了、人間の close 待ち
### Stale ⚠️ (X)
- #<n> <title> — no update for <days> days
### Done (X)
- #<n> <title>
## Recommendations
1. <次に着手を勧めるもの>
2. <ブロッカー解除のための提案>
3. <停滞中の Issue への対応案>
ユーザーが望めば:
plan-dependencies skill で提案自動でコメント・assignee 変更・Status 変更を行わない。提案までに留め、実行はユーザー承認後に明示的に行う。
{
"epic": 100,
"summary": {
"totalStories": 8,
"doneEquivalentStories": 3,
"needReviewStories": 2,
"closedStories": 1,
"percentComplete": 38
},
"buckets": {
"ready": [...],
"inProgress": [...],
"blocked": [...],
"needReview": [...],
"stale": [...],
"done": [...]
},
"recommendations": ["..."],
"nextStep": "Approve and run plan-dependencies to fix blocker chain"
}
plan-dependencies で graph を再評価decompose-epic の方針（全体リリース + 機能別検証）を再確認first: 50 固定なので、それを超える場合は gh api graphql を直接叩く運用に切り替える