check-pr
SolidRead-only inspection of a single GitHub PR lifecycle — checks CI, review threads, description sync, and mergeability, and returns PASS or FAIL with per-gate findings. Never invokes the merge button. Use when verifying a PR is ready to merge, polling lifecycle progress, checking mergeability, or babysitting a GitHub PR through CI and approvals.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- doodledood
- Repository
- doodledood/manifest-dev
- Created
- 8 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
check-pr
Checks a GitHub pull request for unresolved review comments, failing status checks, and incomplete PR descriptions. Waits for pending checks to complete, categorizes issues as actionable or informational, and optionally fixes and resolves them. Use when the user wants to check a PR, address review feedback, or prepare a PR for merge.
pr-gate
Validate a pull request end to end — work out what it actually changes and who it breaks, diagnose and fix a red pipeline, triage agent review comments (fix the valid ones, reply to and resolve the rest), judge whether it is genuinely ready, and merge it when asked. Use this whenever the user points at a PR (a number, a URL, "this PR", a Renovate/Dependabot bump) and wants to know whether it is safe, why a check is failing, whether it can be merged, or wants it merged. Use it for inbound PRs you did not write, dependency bumps, and any "is this ready to merge", "can you merge it", "fix the CI on this PR", "why is this check red", "address the review comments", or "does this break anything" request. For deploying and canary-verifying your own freshly shipped PR, use land-and-deploy instead; for a line-by-line code critique with no merge decision, use code-review.
pr-review
Reviews a branch, PR, staged, or working-tree diff for correctness, security, repo-convention, test-coverage, and documentation gaps, returning severity-rated findings without editing code. Use when asked to "review my branch/PR", "is this ready to merge", "check this diff before I push", "does this need an ADR", or to apply fixes for findings from a previous review round. When the target is a GitHub PR, the same report is also posted to the PR — as inline comments on each finding's line plus a summary, by default — so the whole team can read it.