Menu
Summarize GitHub Epic issue with sub-issues and related PRs. Use when reviewing epic progress or getting implementation overview.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Generic thinking protocol for deriving optimal solutions through iterative self-checking. Invoke BEFORE searching within the given problem space whenever the user asks for advice, judgment, evaluation, or choice. Reframes the problem, generates options, evaluates trade-offs, runs a self-answer check (does this answer the user's actual question at the right granularity, reach upstream, match expectations, offer non-obvious value?), and loops back to upstream tracing or same-level reframing if the check fails — until convergence. Applies across any domain — technical, process, organizational, decision-making, career. Triggers when the user uses evaluation or reconsideration language ("which is best", "root cause", "is this really needed", "sustainable long-term", "ほんとうに", "そもそも", "最善は", "根本は", "筋が良い"), when validating the soundness of someone's proposal from multiple perspectives, when the problem spans multiple layers (tech / process / org / regulation / UX / cost), or when clear trade-offs exist.
Review the local diff with flat-perspective sub-agents, fix findings in a loop, then create a PR via the create-pr skill once the review is clean
計画や設計について、ユーザーを徹底的に問い詰めて一緒に詰める。実装・着手の前に計画をストレステストしたいとき、または「詰めて」「グリルして」「問い詰めて」「ツッコんで」「設計レビューして」「ほんとうにこれでいい?」などのトリガー表現が出たときに必ず使う。
.claude/rules/ 配下のルールファイル (*.md) を新規作成・編集するときに、適切なメカニズム選択と paths スコープを保証する。ルールを書く前・書いた後に必ず適用する。
Orchestrate Epic issue as team leader. Delegate sub-issues to member agents in isolated worktrees. Members run in background and communicate via SendMessage.
Fetch a GitHub issue with its sub-issues, walk up to the parent Epic, list sibling issues under that Epic, fetch the body of each sibling issue, attach the implementing PR for each closed sibling with body and diff summary, gather related code, and present as a Japanese summary so the reader can grasp the whole task context including the actual contents of siblings and their PRs
Based on SOC occupation classification
| name | summarize-epic |
| description | Summarize GitHub Epic issue with sub-issues and related PRs. Use when reviewing epic progress or getting implementation overview. |
| disable-model-invocation | true |
GitHub の Epic Issue とそのサブ Issue、関連 PR を集約してサマリーを生成する。
<epic-issue-url>: GitHub Epic Issue の URL (例: https://github.com/owner/repo/issues/123)
$ARGUMENTS
gh issue view <epic-number> --repo <owner>/<repo> --json subIssues --jq '.subIssues.nodes[].number'
# Epic Summary
## Basic Info
- **Epic**: <url>
- **State**: <state>
- **Assignees**: <assignee-list>
## Overview
<Epic body summary>
## Key Comments
<Important decisions and changes from Epic comments>
## Sub-issue Progress
- **Completed**: <completed>/<total> issues
- **Progress**: <percentage>%
## Implementation Highlights
### Merged Changes
- <pr-url>: <summary of main changes>
### In Progress
- <pr-url>: <change overview>
## Overall Progress
- **Completed**: <completed>/<total> issues
- **Progress**: <percentage>%
- **Remaining**: <pending or in-progress tasks>
## Issues & Gaps
<Discrepancies between Epic spec and implementation, blockers, concerns>
## Next Steps
<Upcoming milestones>
# Epic issue
gh issue view <number> --repo <owner>/<repo> --json title,body,state,comments
# Sub-issues
gh issue view <epic-number> --repo <owner>/<repo> --json subIssues --jq '.subIssues.nodes[].number'
# Related PRs (GraphQL)
gh api graphql -f query='
{
repository(owner: "<owner>", name: "<repo>") {
issue(number: <issue-number>) {
timelineItems(first: 100, itemTypes: [CROSS_REFERENCED_EVENT]) {
nodes {
... on CrossReferencedEvent {
source {
... on PullRequest { number title state merged mergedAt }
}
}
}
}
}
}
}
'
# PR details
gh pr view <pr-number> --repo <owner>/<repo> --json title,body,state,mergedAt,additions,deletions,changedFiles