skills.rest
notque
notqueCOMMUNITY
Explore all skills by this author →
GitHub

pr-status

Report current branch and pull request status with CI results.

415|44|Updated Mar 18, 2026
Search Tags:#git#merge#ci#pull-request#reviews#pr-status
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill pr-status-notque
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-status
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/pr-status
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill pr-status-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps you informed about your current branch and PR state, including local changes, CI results, reviews, and merge readiness, so you know when a PR is ready to merge without switching tools.

Core Features & Use Cases

  • Show current branch and its relation to the base branch
  • Display local working tree state (clean or modified)
  • Retrieve PR metadata (number, title, URL, state)
  • List CI checks with pass/fail status
  • Summarize reviews per reviewer
  • Report merge readiness and conflicts
  • Detect Claude Code review activity

Quick Start

Ask Claude to run pr-status to generate a complete status report for the current branch.

Frequently Asked Questions about pr-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my pull request status including CI checks and reviews?▼

To check pull request status including CI checks and reviews, you can generate a consolidated report that retrieves PR metadata, lists CI pass/fail results, and summarizes reviewer feedback without modifying your repository state.

How do I know if my Git branch is ready to merge without switching tools?▼

To know if your Git branch is ready to merge without switching tools, run a status report that evaluates local working tree changes, CI results, and merge conflicts against the base branch.

What do I need to retrieve PR metadata and CI results for my feature branch?▼

To retrieve PR metadata and CI results for your feature branch, you need Git and the GitHub CLI installed in your environment to access branch state, PR data, and CI information.

Can I get a quick PR health check for a bug fix branch before merging?▼

Yes, you can get a quick PR health check for a bug fix branch, as this reporting mechanism is applicable across feature branches, bug fixes, and release branches to verify merge readiness.

Does this PR status method detect Claude Code review activity?▼

Yes, this PR status method detects Claude Code review activity alongside listing standard per-reviewer summaries and current PR state to provide a complete view of branch health.

What is the best way to view local working tree state and PR CI results together?▼

The best way to view local working tree state and PR CI results together is to generate a single formatted report that identifies whether your working tree is clean or modified and lists all CI checks.

Related Skills

Explore More Software Engineering Skills→
aivos-xieaivos-xie
1

github-pr-workflow

Automate the GitHub Pull Request lifecycle from branch creation to merging.

Community
Advanced
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
BedriftsgrafenBedriftsgrafen

Safe Push

Validate backend and frontend code locally before pushing commits.

Official
Intermediate
openshiftopenshift
71

investigate-ci-failure

Diagnose CI/Prow failures for GitHub PRs using gh CLI data.

Official
Advanced