skills/pr-dashboard/SKILL.md
Open a GitHub PR dashboard in the browser. Use when the user asks to see their pull requests, open the PR dashboard, show PRs for a date range, or check PR status. Trigger phrases include "show my PRs", "open PR dashboard", "pull request dashboard".
npx skillsauth add williamlimasilva/.copilot pr-dashboardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
development
Anxiety-aware, evidence-driven collaboration for stalled or high-stakes work when a user says uncertainty, repeated setbacks, or lack of visible progress is causing significant anxiety or distress. Use immediately when explicitly invoked; when this fit is only inferred from the user's own account, ask permission before applying it. Preserve the user's ideal and turn grounded perspective-taking into persistent, bounded problem solving. Do not use to diagnose, provide therapy, manufacture certainty, or lower goals for reassurance.
development
Build, review, debug, package, and test Roslyn diagnostic analyzers, code fix providers, and incremental source generators. Use for DiagnosticAnalyzer, CodeFixProvider, IIncrementalGenerator, IOperation analysis, Microsoft.CodeAnalysis dependency pinning, Roslyn test harnesses, C#/VB tests, and analyzer NuGet packaging.
testing
Migrates a project that uses checked-in .designer.cs files behind .resx to using a source-generator instead
development
Polish any GitHub repository's surface — labels (emoji rating tiers, P0–P3 priority, impact severity), issue forms, PR template, CI workflows, CODEOWNERS, rulesets, docs. Repo meta & config only — no code logic touched. Use when creating a new repo or polishing an existing one.