菜单
Review open PRs authored by the user for a given repo, showing title, status, review state, open comments, CI checks, and recommended next steps. Use when the user mentions PR review, my PRs, open PRs, PR status, PR dashboard, or wants an overview of their pull requests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | pr-dashboard |
| description | Review open PRs authored by the user for a given repo, showing title, status, review state, open comments, CI checks, and recommended next steps. Use when the user mentions PR review, my PRs, open PRs, PR status, PR dashboard, or wants an overview of their pull requests. |
Generate a status overview of the user's open PRs for a given repository.
The user provides a shorthand name (e.g., "my-app", "api-server"). Resolve it to owner/repo:
gh repo list --json nameWithOwner --limit 200 -q '.[].nameWithOwner' and filter for a repo name containing the shorthand.owner/repo directly, use it as-is.gh pr list --repo OWNER/REPO --author @me --state open \
--json number,title,url,isDraft,reviewDecision,updatedAt,additions,deletions,labels,headRefName
If no PRs are found, report that and stop.
For each PR, fetch detailed review and check info:
gh pr view NUMBER --repo OWNER/REPO \
--json reviewDecision,reviews,comments,statusCheckRollup,mergeable,mergeStateStatus
Assign each PR a single status icon. This icon is used both in the detail rows and in the copy-paste summary. Pick the first matching rule, in priority order:
| Icon | Meaning | Condition |
|---|---|---|
| 🔴 | CI failing | statusCheckRollup has any failing check |
| 🟠 | Changes requested | reviewDecision = CHANGES_REQUESTED |
| 📝 | Draft | isDraft = true |
| 🟡 | Awaiting review | review pending / no reviewers / CI still pending |
| 🟢 | Green — ready to merge | reviewDecision = APPROVED and all CI checks passing |
For each PR, present a row with:
| Field | Source |
|---|---|
| Title | title |
| PR | #number as a markdown link to url |
| Branch | headRefName |
| Size | +additions / -deletions |
| Draft? | isDraft → "Draft" or "Ready" |
| Reviews | Summarize from reviewDecision: APPROVED → "Approved", CHANGES_REQUESTED → "Changes requested", REVIEW_REQUIRED → "Awaiting review", empty → "No reviewers" |
| CI | From statusCheckRollup: count pass/fail/pending. Show "All passing", "N failing", or "Pending" |
| Comments | Count of unresolved review comments from comments and reviews |
| Updated | Relative time from updatedAt |
Derive one recommended action per PR using this priority:
## PR Dashboard: {owner/repo}
### {icon} 1. {title}
- **PR**: [#{number}]({url}) | **Branch**: `{branch}`
- **Size**: +{additions} / -{deletions} | **Updated**: {relative_time}
- **Status**: {Draft/Ready} | **Reviews**: {review_summary} | **CI**: {ci_summary}
- **Open comments**: {count}
- **→ Next step**: {recommendation}
---
(repeat for each PR)
After the detailed report, always end with a copy-paste summary block. This is the part the user drops straight into a Slack message — keep it tight: one line per PR, just the status icon followed by the PR title as a link to its GitHub URL. No branch, size, or extra metadata.
**PR dashboard check — {owner/repo}**
{icon} [{title}]({url})
{icon} [{title}]({url})
{icon} [{title}]({url})
Notes:
[{title}]({url}) so the title is clickable and lands on the PR in GitHub.Sort the detailed report by the same priority order.
Audits and fully configures how a website looks when shared (Open Graph, Twitter/X cards, WhatsApp/Discord/Slack previews) and in the browser (title, favicons, theme-color, web manifest), generating missing assets and verifying the result locally. Use when setting up link previews, og:image, favicons, social sharing metadata, or when a shared link "looks wrong" on a platform.
Iterative React-health loop: inventory every React app in the repo, baseline with the latest react-doctor (pinned for the rest of the run), fix one root cause per iteration, and re-verify until every app scores 100/100 or every remaining finding has a user-approved written justification. Never silences findings with ignores, exclusions, or deleted behavior, and stops itself after two iterations without measurable progress. Use when the user mentions react-doctor, React health score, React anti-patterns cleanup, or driving a React codebase to a clean scan.
Iterative dependency-CVE remediation loop: scan with ecosystem-native advisory tooling, assess whether each high/critical finding is actually reachable (with call-path evidence, not vibes), fix the highest-risk reachable one with the smallest credible change, re-verify, and repeat. Terminates when no exploitable high/critical CVE remains or every remaining finding has an evidence-backed reachability assessment and an approved risk decision. Use when the user mentions CVEs, vulnerability scanning, dependency security, npm/pip/cargo audit, security patching, or wants a recurring dependency-security loop.
Orchestrates a comprehensive frontend UI review by running parallel analysis across typography, layout, accessibility, responsiveness, copy, visual polish, and design critique. Uses browser inspection for visual context. Produces a prioritized plan of small, concrete fixes -- never rewrites. Use when the user mentions UI review, frontend review, page review, design review, visual review, audit my page, or review my UI.
Surfaces the single most important blindspot in a plan, decision, or situation by checking whether the frame is right, generating candidates across 8 lenses (hidden constraints, false assumptions, second-order effects, stakeholders, blast radius, base rates, time horizon, counter-positions), then either committing to one or returning a calibrated "no blindspot" when none is load-bearing -- never a list of risks. Use when the user asks "what am I missing", "what's the most important thing I'm missing about this situation or decision", "what's my blindspot", "what's the biggest risk I'm not seeing", or wants a single sharp second opinion before committing.
Read-only audit of a web page's layout grid. Measures column adherence, baseline rhythm, and optical ink alignment in pixels (Müller-Brockmann), then critiques grid appropriateness, type scale, flush-left, white space, measure, and color-as-identifier (Vignelli). Mechanical px violations first, principled critique second, each with a minimal fix -- never rewrites. Works rigorously on pages with a declared CSS grid; falls back to inferred-grid plus principled checks on arbitrary pages. Use when the user mentions grid review, grid audit, layout grid, column alignment, baseline grid, is my grid aligned, Swiss grid, Müller-Brockmann, or Vignelli.