From Napkin
Opens a GitHub PR dashboard in the browser filtered by date range and role (authored, reviews, assigned).
How this skill is triggered — by the user, by Claude, or both
Slash command
/napkin:pr-dashboardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generates and opens a GitHub PR dashboard in the browser for a given date range and role filter.
Generates and opens a GitHub PR dashboard in the browser for a given date range and role filter.
Prerequisites: GitHub CLI (gh) must be installed and authenticated (gh auth login).
Find the CLI script bundled with this skill and run it:
SKILL_SCRIPT=$(find ~/.copilot -name "pr-dashboard-cli.mjs" -path "*/pr-dashboard/scripts/*" 2>/dev/null | head -1)
node "$SKILL_SCRIPT" "<query>" "<role>"
<query>: the date range the user specified (default: last 7 days)<role>: one of Authored by me, Requested reviews, Assigned to me, All (default: Authored by me)Extract the date range and role from the user's message. Examples:
| User says | query | role |
|---|---|---|
| show my PRs | last 7 days | Authored by me |
| show my PRs last 2 weeks | last 2 weeks | Authored by me |
| PR dashboard this month reviews | this month | Requested reviews |
| PR dashboard march 2026 assigned | march 2026 | Assigned to me |
| show all PRs last 30 days | last 30 days | All |
Role keyword mapping:
Authored by meRequested reviewsAssigned to meAllThe script understands natural language — pass it through as-is:
last 7 days, last 2 weeks, last 30 daysthis week, last week, this month, last monthmarch 2026, feb 20252026-01-01 - 2026-03-312025 (whole year)Tell the user the dashboard is opening in their browser. The script outputs progress to stdout. If it exits with an error, show the error output and suggest they run gh auth login if it's an auth issue.
npx claudepluginhub ani1797/forge --plugin copilot-sdk3plugins reuse this skill
First indexed Jun 6, 2026
Terminal-based GitHub PR dashboard showing CI/CD progress, bot comments, file changes, and one-command merges.
Structured, filtered PR retrieval via context_query_prs. Use this instead of context_search_prs when you need a precise filtered list — scoped by project/repo and/or person — rather than semantic relevance matching. TRIGGER when: the user asks "what PRs did Alice open last week", "list merged PRs in payments-service this month", "PRs I'm waiting on review for", "what did the team ship yesterday"; you need a definitive list rather than a ranked set; you already know the repo name or person and want to enumerate PRs under that filter. DO NOT TRIGGER when: the question is conceptual ("why was this introduced", "what PR added feature X") — use context-search-prs for semantic matching instead.
Queries GitHub PRs, issues, workflow runs, and repo metadata via `gh` CLI with JSON output. Use for inspecting PR checks, fetching failed CI logs, or resolving github.com URLs to API calls.