pr-summary
PR Summary
List open PRs, filter automation PRs (dependabot/snyk), group by ticket ID, output formatted summary.
When NOT to Use
| Scenario | Use Instead |
|---|---|
| Create a new PR | /create-pr |
| Review PR code | /codex-review |
| View single PR details | gh pr view <N> |
| Pre-merge analysis | /merge-prep |
Input
/pr-summary [--author <user>] [--label <label>]
| Argument | Description | Default |
|---|---|---|
--author <user> |
Filter by author | All |
--label <label> |
Filter by label | All |
Workflow
1. Run Script
bash skills/pr-summary/scripts/pr-summary.sh [--author <user>] [--label <label>]
The script automatically:
| Step | Action |
|---|---|
| Fetch | gh pr list --json to get open PRs (max 200) |
| Filter | Exclude dependabot/* and snyk-* |
| Group | Group by ticket ID ({TICKET_PATTERN} or [A-Z]+-\d+) |
| Detect | Identify stacked PRs (base is not main/master/develop) |
| Output | Write formatted text to /tmp/pr-summary.md |
2. Display Results
Read /tmp/pr-summary.md and display to user.
3. Provide Copy Instructions
Content written to /tmp/pr-summary.md
Copy: cat /tmp/pr-summary.md | pbcopy
Output Format
Markdown (default)
**PROJ-520**
https://github.com/user/repo/pull/123
> fix: Add Redis cache for contract codes
https://github.com/user/repo/pull/124
> fix: Tune server timeouts (stacked on fix/PROJ-520)
**PROJ-123**
https://github.com/user/repo/pull/99
> feat: Add DeFi portfolio tracking
Grouping Rules
| Condition | Strategy |
|---|---|
| Same ticket ID | Same group |
| Stacked PR (base is feature branch) | Same group, annotate (stacked on <base>) |
| No ticket / unrelated | Standalone entry |
Filter Rules
| PR Source | Action |
|---|---|
dependabot/* |
Exclude |
snyk-* |
Exclude |
| Others | Keep |
References
| File | Purpose |
|---|---|
| pr-summary.sh | PR fetch, filter, group, format script |
Verification
- Lists all open PRs (excluding dependabot/snyk)
- PRs grouped by ticket ID
- Stacked PRs annotated with dependency
- Output format is valid Markdown
-
/tmp/pr-summary.mdwritten
More from sd0xdev/sd0x-dev-flow
statusline-config
Customize Claude Code statusline. Use when: user says 'statusline', 'status line', 'customize statusline', 'modify statusline', 'statusline settings', 'statusline theme', 'change theme', 'color scheme', wants to add/remove/change segments (cost, git, model, context), switch color themes (catppuccin, dracula, nord), or asks what can be shown in the statusline.
52tech-spec
Tech spec generation and review. Use when: designing features, writing specs, spec review. Not for: requirements analysis (use req-analyze), implementation (use feature-dev), architecture advice (use codex-architect). Output: numbered tech spec document.
45codex-brainstorm
Adversarial brainstorming via Claude+Codex debate. Use when: exploring solutions, feasibility analysis, exhaustive enumeration. Not for: implementation (use feature-dev), architecture only (use codex-architect). Output: Nash equilibrium consensus + action items.
7security-review
Security review via Codex MCP. Use when: OWASP Top 10 audit, dependency vulnerability check, security-sensitive changes. Not for: code review (use codex-code-review), test review (use test-review). Output: security findings + audit report.
7test-review
Test coverage review via Codex MCP. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
7post-dev-test
Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.
6