My Pull Requests
Get a personal digest of pull requests assigned to you in the current repo, including review blockers, failed checks, and optional Copilot review offers.
Overview
my-pull-requests is an agent skill most often used in Ship (also Build PM-style tracking) that lists and explains your assigned PRs in the current GitHub repository.
Install
npx skills add https://github.com/github/awesome-copilot --skill my-pull-requestsWhat is this skill?
- Uses #githubRepo for context and #list_pull_requests to find PRs assigned to you
- Summarizes purpose and details for each pull request
- Calls out PRs waiting on a human reviewer
- Describes check failures and suggests plausible fixes
- Offers #request_copilot_review when Copilot has not reviewed yet
- 5 response obligations: list, describe, highlight review waits, explain check failures, offer Copilot review
Adoption & trust: 9.8k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You do not know which PRs are yours, what state they are in, or whether reviews and checks are blocking merge.
Who is it for?
Indie devs juggling multiple PRs in one repo who want a quick assigned-to-me snapshot inside the agent.
Skip if: Org-wide PR dashboards, repos without GitHub list_pull_requests tooling, or deep line-by-line review replacement.
When should I use this skill?
List my pull requests in the current repository and summarize status, reviews, and checks.
What do I get? / Deliverables
You receive an ordered, human-readable PR status report with review gaps, check failures, and optional Copilot review next steps.
- Narrative summary of each PR assigned to you
- Action hints for review waits, failed checks, and Copilot review requests
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
PR status and review readiness are central to shipping safely—the primary shelf is Ship → review. The workflow searches the repo, lists assigned PRs, and surfaces review and CI state—classic pre-merge review hygiene.
Where it fits
Scan assigned PRs for reviewer stalls and failing checks before you merge to main.
Decide which open PR to finish first based on CI green and review coverage.
Check whether a hotfix PR you opened still needs Copilot or human review after deploy.
How it compares
Assigned-PR inbox summary via GitHub tools—not a full PR description generator or merge bot.
Common Questions / FAQ
Who is my-pull-requests for?
Solo and small-team builders using GitHub Copilot-style agents who need a fast view of PRs assigned to them in the active repo.
When should I use my-pull-requests?
At Ship review before standup or merge day; during Build pm when prioritizing which branch to finish; after pushing when you forgot open PR state.
Is my-pull-requests safe to install?
It triggers read-oriented GitHub tool use in your connected repo; review the Security Audits panel on this Prism page and your token scopes.
SKILL.md
READMESKILL.md - My Pull Requests
Search the current repo (using #githubRepo for the repo info) and list any pull requests you find (using #list_pull_requests) that are assigned to me. Describe the purpose and details of each pull request. If a PR is waiting for someone to review, highlight that in the response. If there were any check failures on the PR, describe them and suggest possible fixes. If there was no review done by Copilot, offer to request one using #request_copilot_review.