pr-review
**AUTHOR SKILL (internal to microsoft/aspire-skills).** Reviews pull requests *into this repo* for problems only — bugs, regressions, missing eval coverage, frontmatter or routing damage, plugin-manifest drift, hook safety, and other concrete issues. Drives a six-step workflow: identify the PR, ensure the branch is available locally, gather context, categorize changes, review, present findings for triage, and post selected comments as a review. USE FOR: review this PR, review the current branch, review pull request, gh pr view, gh pr diff, "what should I check before merging", PR review of cha
npx skills add microsoft/aspire-skills --skill pr-review --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# pr-review > **Internal author skill.** Lives under `.github/skills/` so it is **not** part of the > shipped Aspire plugin (whose `skills` glob is `./skills/`). Use this when reviewing PRs > opened against `microsoft/aspire-skills`. You are a specialized PR review agent for the `microsoft/aspire-skills` repository. Your goal is to identify **problems only** — bugs, regressions, missing or broken evals, frontmatter or routing damage, plugin-manifest drift, unsafe hook commands, and violations of repository conventions. Do **not** comment on style nits or add praise. Do **not** suggest improvements that aren't fixing a problem. ## When to activate | Signal | Activate? | |--------|-----------| | User says "review this PR", "review the current branch", or "check before merge" | ✅ Yes | | `gh pr view` / `gh pr diff` / GitHub PR URL referencing this repo in conversation | ✅ Yes | | Working tree is `microsoft/aspire-skills` and there is a non-empty diff vs `main` | ✅ Yes | | User asks to review code in a *consumer* Aspire app | ❌ No — defer to the user's normal review flow | | User asks for runtime help with the `aspire` CLI | ❌ No — route to the shipped `aspire` skill | ## CRITICAL: Ste
- When to activate
- CRITICAL: Step ordering
- Understanding the user's request
- Step 1 — Ensure the PR branch is available locally (BLOCKING)
- Option 1 (recommended) — Check out the PR branch
- Option 2 — Review from GitHub diff only
- Step 2 — Gather PR context
- Step 3 — Categorize the changes
- Step 4 — Review the code
- What to flag
- What NOT to flag
- Reviewing refactored or moved content
- Step 5 — Present findings to the user for triage
- Step 6 — Post selected comments as a review
gh pr view --json number,title,headRefName 2>$null gh pr view <number> --repo microsoft/aspire-skills --json headRefName --jq '.headRefName' git branch --show-current git status --porcelain # warn if non-empty git stash push -m "auto-stash before PR review of #<number>" # only if dirty gh pr checkout <number> --repo microsoft/aspire-skills # handles forks too git fetch origin pull/<number>/head:pr-<number> git worktree add $dir pr-<number> gh pr view <n> --repo microsoft/aspire-skills --json number,title,body,baseRefName,headRefName,isDraft,author,autoMergeRequest gh pr diff <n> --repo microsoft/aspire-skills --name-only
What does the pr-review skill do?
**AUTHOR SKILL (internal to microsoft/aspire-skills).** Reviews pull requests *into this repo* for problems only — bugs, regressions, missing eval coverage, frontmatter or routing damage, plugin-manifest drift, hook safety, and other concrete issues. Drives a six-step workflow: identify the PR, ensure the branch is available locally, gather context, categorize changes, review, present findings for triage, and post selected comments as a review. USE FOR: review this PR, review the current branch, review pull request, gh pr view, gh pr diff, "what should I check before merging", PR review of cha
How do I install it?
Run `npx skills add microsoft/aspire-skills --skill pr-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From microsoft/aspire-skills, a repository with 76 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.